Re:Universal XSS in uBlock Origin from website-driven elemen...
by negura on Sunday November 15, 2026 @11:20PM
(#50513986)
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.
[ Parent
| on HN ]
Re:Universal XSS in uBlock Origin from website-driven elemen...
by canicollectongo on Sunday November 15, 2026 @11:24PM
(#50514023)
Th day no browser allows it is the day I make the vibe-browser. A browser that scraps all the content of every website, and tells an AI to present it without the garbage.
This extensions exist to solve a problem where the alternative will NOT involve playing nice about it.
Re:Universal XSS in uBlock Origin from website-driven elemen...
by numpad0 on Monday November 16, 2026 @03:17AM
(#50515263)
[delayed]
Re:Universal XSS in uBlock Origin from website-driven elemen...
by Telaneo on Sunday November 15, 2026 @11:23PM
(#50514015)
The same can be said about websites themselves.
Re:Universal XSS in uBlock Origin from website-driven elemen...
by negura on Sunday November 15, 2026 @11:43PM
(#50514132)
Individual websites can't be granted permission over your entire browser, they operate in a sandbox (then again firefox for example has a relatively insecure sandbox).
Re:Universal XSS in uBlock Origin from website-driven elemen...
by madeofpalk on Sunday November 15, 2026 @11:55PM
(#50514191)
Well no not really. There’s strong cross-origin restrictions in browsers to prevent anything bad happening just because you visit a website.
Web extensions are troubling because they tend to have pretty unfettered access to one of the most sensitive parts of your computer.
Re:Universal XSS in uBlock Origin from website-driven elemen...
by AnthonyMouse on Monday November 16, 2026 @02:54AM
(#50515146)
We're talking about bugs here. If the website has a bug you're not just compromising one user. Input sanitizing bug, or the site even just makes the mistake of hosting user-uploaded content on the same domain as the main site, and the attacker can upload javascript that then gets run under the origin of the main site. Attacker can now capture other users' passwords or otherwise take control over their accounts because the user visited the main site with the bug rather than needing to visit the attacker's. Many of those passwords will have been reused on other sites.
Meanwhile an extension can't do anything the browser can't do, so why is it a problem for the extension but not the browser itself?