deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

uBlock Origin's universal XSS is fixed, but many installs never auto-updated

A universal XSS in uBlock Origin let any visited site plant a trusted scriptlet filter and run JavaScript in other sessions. Fixes are out, but users report the extension often failed to auto-update.

uBlock Origin's universal XSS is fixed, but many installs never auto-updated

Universal XSS, fixed but not necessarily deployed

uBlock Origin has fixed a universal cross-site scripting flaw that let any website you visited run JavaScript inside your sessions on other sites, including webmail or GitHub. The bug, reported by researcher Smitty van Bodegom, was patched in uBlock Origin 1.75.4 and hardened further through 1.76.4. The catch, according to a dev.to writeup by Alan West, is deployment: several people in the related Hacker News discussion found their copy of the extension had not updated itself, leaving them on a vulnerable build days after the fix shipped.

How the attack chain worked

Bodegom's writeup describes a five-step chain. On Firefox, extension pages live under a per-install moz-extension URL containing a random UUID that is supposed to stay secret. One of uBO's default filters, an anti-adblock countermeasure, answers a blocked request by fetching a replacement script from the extension over XHR, and that request runs through the page's own XMLHttpRequest. An attacker who hooks XMLHttpRequest.prototype.open and trips the filter can simply read the UUID out of the request URL; on MV2 Chromium builds the same hook also exposed a web-accessible-resources secret, per the GitHub advisory.

With the secret in hand, the attacker page embeds uBO's element picker in an iframe. The root cause, per the writeup, is that the picker accepted messages from any page rather than only from uBO's own content script. Over a MessageChannel the attacker starts the picker, then sends messages that enable the Create button and set its option field. That field normally holds a request type such as image, appended to the filter after a $, but newlines were never stripped. A value like image followed by a newline and google.com##+js(trusted-rpnt, ...) therefore becomes two lines: one harmless network filter and a trusted scriptlet that rewrites script content on a chosen domain.

Filters created through the picker are treated as trusted until the next recompile, and the page can render the iframe invisible so the victim's click lands on Create. The advisory quotes the report as saying the site only needs the user to click anywhere. The 1.75.4 fix is direct: the real content script hands the picker a secret token, and the picker refuses to start without it.

Which versions are affected

According to the GitHub security advisory GHSA-cmqw-9r2w-6wv2, rated High with no CVE and published November 15, 2026, uBlock Origin 1.75.2 and lower are vulnerable, with the first fix in 1.75.4 released November 3. West recommends going to 1.76.4 or later because the fix landed in layers: 1.76.0 (November 8) validated the filter the picker creates and blocked war:-related filters, while 1.76.4 (November 15) addressed remaining reported issues and removed the now-unused warOrigin and warSecret values. The reporter also speculated about a possible race when uBO injects into a late-loading iframe, though it could not be reliably reproduced.

uBO Lite, the MV3 edition for Chrome and Edge, had what the researcher called a similar but less problematic issue, fixed in build 2026.1110.1816 on November 10. West notes that version comes from the release notes and Hacker News commenters, since the advisory itself covers only uBlock Origin. Beta builds of 1.76.5 go further and place overlay tools like the picker inside a shadow DOM.

How to check and force the update

The version number is visible in the uBO dashboard's About tab, or via about:addons in Firefox, chrome://extensions in Chrome and edge://extensions in Edge. To force an update: in Firefox, open about:addons, use the gear menu and choose Check for Updates — one commenter reported needing two attempts to reach 1.76.4. In Chrome and Edge, enable Developer mode on the extensions page and click Update. Firefox for Android reportedly has no manual update control, so the workaround is to remove and reinstall the extension, backing up settings first via Dashboard, Settings, Back up to file.

If you ran a vulnerable build

An attack would leave a filter behind. Check the My filters pane for anything unfamiliar, especially lines containing ##+js( or trusted- scriptlets such as trusted-rpnt, then delete them and apply changes. Editing custom filters also triggers a recompile, which clears the trusted status that picker-created filters receive. If updating is not possible right away, disabling the extension on untrusted sites is the safer option.

Why it matters

A security tool became the attack vector: the anti-adblock countermeasure inside a default filter handed over the secret that unlocked the extension's privileged UI. The episode also shows that extension auto-updates cannot be assumed, since users who believed they were current were not, and that privileged UI rendered inside web pages is an architectural risk shared by other extensions with in-page overlays. Checking a version number takes seconds; recovering a hijacked mail or code-hosting session does not.

  • #ublock-origin
  • #browser-extensions
  • #security
  • #xss
  • #firefox

Related posts