uBlock Origin Element Picker flaw enables UXSS via trusted filter injection; fixed in 1.75.4 and later
The uBlock Origin ad-blocking extension was patched for a high-severity cross-site scripting (UXSS) flaw. Per the article, a malicious website could embed and control the extension's Element Picker under specific filter conditions. A victim's click would then save attacker-crafted trusted scriptlet rules, which can run arbitrary JavaScript on unrelated domains. The article says the flaw affects versions up to 1.75.2 and that the developer fixed it privately before disclosure. No exploitation in the wild is reported. No CVE is named, and no vendor advisory or other primary source was checked.
Entenda a falha
A vulnerabilidade
A high-severity universal cross-site scripting (UXSS) flaw in the Element Picker of the uBlock Origin extension, with no CVE assigned. Under specific filter conditions, a malicious website can embed and control the picker. The attacker needs the victim to visit the page and click, for example on a fake Cloudflare or Google verification prompt (clickjacking). The click saves attacker-crafted rules as trusted scriptlet filters, which can run arbitrary JavaScript on unrelated sites. Versions 1.75.2 and earlier are affected; 1.75.4 (3 November) fixed the main vector, and 1.76.0 and 1.76.4 added further hardening.
Como funciona
Normally the Element Picker lets the user select elements on a page and turn them into content-blocking rules. Under specific filter conditions, a rogue site can embed the picker interface in a frame and control it. When the victim clicks the embedded frame, the picker registers the attacker-crafted rules as trusted filters. Those trusted scriptlet rules are then allowed to run JavaScript on other, unrelated websites. It does not trigger on its own; the click is required.
Por que é vulnerável
The articles do not give the exact code-level root cause. What they describe is that a web page could embed and drive the picker, and that rules created through it were saved as trusted filters, with privileges to run scripts on other domains. The fix in 1.75.4 closed the main cross-site scripting vector, and 1.76.0 and 1.76.4 added stricter filter validation and architectural safeguards.
Como foi descoberta
A security researcher found it, initially suspecting that filter injection could escalate to universal cross-site scripting. The researcher used GPT-5.6 Sol to speed up root-cause analysis and then verified the exploit chain manually. After the report, the uBlock Origin developer confirmed the issue and fixed it privately before public disclosure. No exploitation in the wild is reported.
PoC existente, privada
O exploit existe, mas quem o tem não o publicou.
The researcher built a proof of concept, with Claude models generating most of its code. It omitted a full deceptive interface, though the article says weaponizing it with clickjacking would be trivial. The articles do not say it was published, so it is treated as private. No exploitation in the wild is reported, but with the click-based vector described, users should still update to 1.76.4.
Explicação gerada por IA a partir da matéria e dos artigos, em 17/11/2026 07:15.
Detalhes técnicos
The attack needs user interaction: the victim must be lured to a malicious page and click, for example on a fake Cloudflare or Google verification prompt (clickjacking). It cannot trigger automatically. The researcher used GPT-5.6 Sol for root-cause analysis, and Claude models generated most of the proof-of-concept code.
Remediação
The article gives the primary fix as 1.75.4 (3 November). Versions 1.76.0 and 1.76.4 added stricter filter validation and further safeguards. It recommends upgrading to 1.76.4, and manual (sideloaded) installs must overwrite their old files from the official GitHub releases page.
Linha do tempo
-
uBlock Origin Element Picker flaw enables UXSS via trusted filter injection; fixed in 1.75.4 and later
ler a análise desta fonte ocultar
The uBlock Origin ad-blocking extension was patched for a high-severity cross-site scripting (UXSS) flaw. Per the article, a malicious website could embed and control the extension's Element Picker under specific filter conditions. A victim's click would then save attacker-crafted trusted scriptlet rules, which can run arbitrary JavaScript on unrelated domains. The article says the flaw affects versions up to 1.75.2 and that the developer fixed it privately before disclosure. No exploitation in the wild is reported. No CVE is named, and no vendor advisory or other primary source was checked.
Technical Details
The attack needs user interaction: the victim must be lured to a malicious page and click, for example on a fake Cloudflare or Google verification prompt (clickjacking). It cannot trigger automatically. The researcher used GPT-5.6 Sol for root-cause analysis, and Claude models generated most of the proof-of-concept code.
Remediation
The article gives the primary fix as 1.75.4 (3 November). Versions 1.76.0 and 1.76.4 added stricter filter validation and further safeguards. It recommends upgrading to 1.76.4, and manual (sideloaded) installs must overwrite their old files from the official GitHub releases page.