{
  "id": 20302595,
  "title": "uBlock Origin's picker flaw and the authorization fix explained",
  "url": "https://urgent.news/2026/11/16/ublock-origins-picker-flaw-and-the-authorization-fix-explained",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-16T17:15:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/axrisi/ublock-origins-picker-flaw-and-the-authorization-fix-explained-2jnj"
  },
  "original_language": "en",
  "account": "uBlock Origin recently patched a flaw in its element-picker feature that could allow a malicious webpage to save trusted filters and execute scripts in another site's context. The key takeaway is understanding the boundary between an extension's interface and the website it interacts with. This interface can be controlled by the extension, while still needing to reject commands from the webpage. Earlier, this boundary was not adequately protected, allowing a potential security vulnerability.\n\nThe repair process involved changing the authority boundary, requiring a verified secret token to activate the picker. Before this fix, the picker would accept commands from a webpage, treating the saved rules as trusted. These rules could inject JavaScript into a webpage, potentially influencing behavior on other sites beyond the initially selected element. If an extension owner owns the interface and controls the messages sent to it, then a malicious page could exploit this to add unauthorized rules to the trusted filter store, targeting other websites and executing scripts in their context.\n\nThe reported exploit involved returning an extension resource as a substitute for an unwanted network response, which could expose the extension's internal identifier. A hostile page could then load the picker interface and send it messages, crossing a website boundary through this authority transfer. The researcher did not implement a hidden overlay, but demonstrated how an ordinary click could activate the picker and create rules beyond what the standard interface allows. There is no evidence of active exploitation or specific victim counts mentioned, so it is important to maintain a cautious stance when summarizing these findings.",
  "summary": "uBlock Origin patched a website-driven element-picker flaw that could let a hostile webpage save trusted filters. Those filters could run script in another site's context. For developers, the useful part of the story is the authority boundary: an interface owned by an extension can be reachable from a page while still needing to reject that page's commands. The maintainer's repair history shows…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 2,
    "also_reported_by": [
      {
        "outlet": "Lobsters",
        "title": "Universal XSS in uBlock Origin from website-driven element picker",
        "url": "https://urgent.news/2026/11/16/universal-xss-in-ublock-origin-from-website-driven-element-picker-20262284",
        "published": "2026-11-16T05:12:27.000Z"
      }
    ]
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}