Universal XSS in uBlock Origin from website-driven element picker
zaik
222 points
54 comments
November 16, 2026
Related Discussions
Found 5 related stories in 124.7ms across 12,728 title embeddings via pgvector HNSW
- Domain hacks with unusual Unicode characters (2018) n_plus_1_acc · 69 pts · November 01, 2026 · 49% similar
- Google Has Removed MV2 Extensions from the Chrome Web Store, Including UBO twapi · 638 pts · August 31, 2026 · 49% similar
- uBlock Origin Lite is back on Firefox add-ons speckx · 38 pts · October 05, 2026 · 47% similar
- Reddit Now Blocking Firefox for Android with uBlock Origin? chucksmash · 19 pts · September 12, 2026 · 47% similar
- The Future of CSS soheilpro · 171 pts · October 21, 2026 · 46% similar
Discussion Highlights (13 comments)
SoftTalker
uBlock Origin has broad permission to inspect and modify anything on a page (it needs it, to do what it does). This would seem to make any vulnerability easier to exploit.
taylorfinley
Really love the "I wrote all the prose, gpt wrote the POC" disclaimer, I would love to see more of those kinds of signals on human authored content.
ethersteeds
> But the attacker website can itself hook the XHR made from inside the no-fetch-if hook to extract the random extension UUID. Oh great. I recently learned[0] that some Firefox extensions can be tricked into leaking their install-unique UUID, which can then be used as a tracking identifier. Today I learn that any site can get my unique uBO UUID by hooking fetch('/adsbygoogle.js'). That is... an ironic disaster. [0] https://news.ycombinator.com/item?id=50454639
TZubiri
Software professionals should uninstall a javascript plugin that runs on every website whose purpose is to consume content more comfortably.
afavour
I understand why folks railed against web extension lock downs that blocked directly editing page content but this is a great example of why it’s a powder keg.
ByteOfWood
I never really loved how extensions have to put their interfaces in the website's DOM if they want to be able to work with the page's elements, like this selector, or a password manager's suggested logins. Especially in the password manager's scenario, it could leak what accounts you have to a given website to that website itself, if the page is looking for new DOM elements. Not exactly a showstopper vulnerability, but it's not a good thing.
jeffbee
Manifest V3 wins again
akersten
So this seems totally solvable by the create-rule element living in the browser chrome instead of the website DOM... why aren't we doing that?
tux
I recommend to delete old forefox profiles and create new once, than install new fixed uBlock0. You should always use separate profiles for all tasks with hardened user.js anyway. Don’t forget to save your bookmarks. Anynew profile creates new UUID.
maplet
Good day to use EWW
forgotmypw17
For those checking (I still had the vulnerable version), you should be at these versions or higher: uBlock Origin: 1.75.4 uBO Lite: 2026.1110.1816
usr1106
Haven't used any uBlock for many years. Use DNS based blocking. For many years I was a happy user of CAD (Cookie Auto Delete). Unfortunately it seems unmaintained. I have now stopped to install it. Don't understand enough of modern browsers to even have an educated guess what kind of vulnerabilities could be buried in the old code.
negura
The concept of browser extensions seems terrible in general. There are many that ship with malware, botnets, infostealers etc. uBlock Origin even requires a compiled .wasm module. It's unwise to grant that level of complexity from third party devs permission over something as sensitive as your web browser.