Smitty van Bodegom disclosed a uBlock Origin flaw that let a malicious website control the extension’s element picker. That is the interface used to select page elements to block. A click could authorize an attacker-chosen trusted filter, allowing JavaScript to run in another website’s context.

The maintainer’s advisory, GHSA-cmqw-9r2w-6wv2, lists 1.75.2 and lower as affected and 1.75.4 as patched. It records that fix’s release on November 3, followed by further filter validation and restrictions in 1.76.0 on November 8. The public advisory and research post appeared November 15. This is a newly disclosed issue with an already released fix.

The website crossed into extension authority

The report centers on the Firefox Manifest V2 extension, the full uBlock Origin rather than uBO Lite. Exploitation required a suitable active filter that exposed an extension resource, a malicious page and a user click. The researcher says a rule in the default filter setup supplied the resource condition on the demonstration domain.

The picker accepted messages from the page without verifying that its legitimate controller sent them. Filters created there were temporarily treated as trusted, giving attacker-controlled input more authority than ordinary website content. The fix authenticates picker startup with a secret token; later hardening also validates the proposed filter.

Evidence status: a researcher-verified demonstration acknowledged and patched by the maintainer. The researcher describes hiding the picker to capture an ordinary click as a possible extension of the demonstration. He says he did not implement that concealment. Neither reviewed source reports exploitation in the wild or a measured number of compromised users.

Check the extension’s installed version

Inspect uBlock Origin’s version in the browser’s add-on manager and apply the current official extension update. 1.75.4 is the advisory’s minimum patched version; current releases also include the later hardening. Updating Firefox alone does not establish that its extensions have updated.

The researcher also mentions a less severe issue in uBO Lite. Its release numbers and capabilities differ, so the full extension’s 1.75.4 threshold should not be applied to Lite or to forks.

What the thread adds

In the Hacker News discussion, bita_nidir and forgotmypw17 report finding an older extension still installed. Those are individual reports, but they explain why checking the actual version matters. l2dy replies with the maintainer’s advisory confirming the patched 1.75.4 threshold.

ByteOfWood raises a wider design concern about extension interfaces embedded inside a website’s page structure. Their follow-up test of Bitwarden narrows the concern: “I was not able to get any data from the extension’s iframe”. They report detecting the extension’s presence, while its account data remained inaccessible in that test. This is a commenter’s observation about a different extension, not a security audit or another demonstrated data leak.

esprehn describes an unrealized “extension overlay API” intended to separate extension interfaces from website content. That design proposal remains distinct from the patched uBlock vulnerability.

HN handles are pseudonymous; comment order is HN’s ranking, not per-comment votes or consensus.

Caveat: the demonstrated cross-site script capability is serious, but the sources do not show that every uBlock installation was reachable or attacked.