ZeroHour
GBHackerspublished ()ingested Divya

FortiPAM Chrome Extension Vulnerability Lets Malicious Sites Control Browser Proxy and Record Tabs

AI summary · glm-5.3-flash

Fortinet patched CVE-2026-84388 (CVSS 9.1) in its FortiPAM Chrome extension, letting malicious websites alter proxy settings, open tabs and record sessions.

The Fortinet FortiPAM Chrome extension flaw (CVE-2026-84388, CVSS 9.1) lets attacker-controlled domains be trusted as FortiPAM servers because a webRequest listener adds requested hostnames without verifying the initiator. A second issue exposes the extension's message interface to all URLs and accepts non-JWT tokens without validation, enabling unauthenticated session launches, proxy manipulation, tab control and recording; the consent dialog can also be bypassed via shadow-root clicks. Fortinet issued advisory FG-IR-26-168 after a July 17 report and released a fix on August 1, 2026, with no confirmed exploitation in the wild.

  • webRequest listener trusts hostnames without validating initiator, letting attacker domains pose as FortiPAM servers
  • externally_connectable all_urls plus token validation gaps allow unauthenticated session launches and proxy control
  • Consent dialog rendered in page DOM can be auto-accepted via shadow-root clicks
  • Fix released August 1 in advisory FG-IR-26-168; no in-the-wild exploitation confirmed
VendorsFortinet
ProductsFortiPAM
OrganizationsAm I Being Pwned

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-84388

NVD description · AI analysis pending
Full article495 words · extracted from gbhackers.com · click to collapse

A critical vulnerability has been identified in the Fortinet FortiPAM Chrome extension that could allow a malicious website to manipulate browser proxy settings, open tabs at the attacker’s discretion, and record activity within those tabs.

This issue, tracked as CVE-2026-84388 and rated with a CVSS score of 9.1, impacts an extension that facilitates privileged access sessions, putting sensitive credentials, API keys, and other data displayed in the affected tabs at risk.

FortiPAM Chrome Extension Vulnerability

The extension typically gets its configuration from a FortiPAM server, which launches target systems, injects credentials, enforces proxy policies, and optionally records activity for auditing.

According to the technical disclosure from Am I Being Pwned, the vulnerability stems from a flaw in the trust mechanism. Specifically, a webRequest listener that monitors requests to /api/v2/monitor/web-ui/state adds the requested hostname to a list of trusted servers without verifying the request initiator or confirming the request completed successfully.

As a result, an attacker could persuade the victim’s browser to regard a domain under the attacker’s control as a legitimate FortiPAM server.

Another issue allows for unauthenticated session launching. The extension’s message interface is exposed through an externally_connectable setting of <all_urls>, permitting arbitrary sites to send runtime messages.

The token-handling mechanism accepts non-JWT values and skips validation instead of rejecting them outright. This means a malicious page could issue a launcher request with its own origin, a fabricated access token, and session parameters.

The extension would then retrieve the full session configuration from that origin, letting the attacker manipulate proxy settings, select the destination tab, and control the recording process.

Researchers also discovered that the extension’s consent control can be bypassed. The permission dialog appears within the page’s main-world DOM, allowing hostile JavaScript to locate the modal’s shadow root and programmatically click the “Allow” button.

When consent is automatically granted this way, the attacker can open a page of their choice and send screen recordings to their own infrastructure. This creates a straightforward phishing opportunity: a victim only needs to view sensitive information in the tab the attacker opens for it to be captured.

Fortinet issued an advisory (FG-IR-26-168) after receiving the report on July 17, with a fix released on August 1. No confirmed cases of exploitation in the wild have been reported.

Although HTTPS complicates proxy-based interception, because an attacker still has to deal with certificate and transport protections, the tab-recording capability could directly expose sensitive information displayed during a browser session.

Organizations should urgently update their FortiPAM Chrome extension deployments, identify users running the affected versions, and review privileged session logs for unexpected launches, proxy changes, or recordings sent to unapproved endpoints. Also verify that every managed browser has received the necessary remediation.

Keep your SOC up to date on active malware & phishing within 24h of their emergence. Try ANYRUN to prevent incidents with early detection

Divya

Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Text extracted automatically; images, tables and formatting may be missing. Original: https://gbhackers.com/fortipam-chrome-extension-vulnerability/