WeSearch

CSS: The bomb inside your inbox

·39 min read · 0 reactions · 0 comments · 6 views
CSS: The bomb inside your inbox
TL;DR · WeSearch summary

The article examines how webmail clients render untrusted CSS and how attackers can exploit sanitization flaws to breach security. It details techniques such as abusing HTML labels, CSS pseudo‑elements, and image proxy bypasses to exfiltrate tokens, hijack accounts, and steal passwords across services like Fastmail, Gmail, and Outlook. The author also discusses defenses and future attack vectors.

Key facts
About this source

Hacker News (Front Page) files mainly under programming. We currently carry 1,295 of its stories. Top-voted stories on Hacker News.

Original article
PortSwigger Research
Read full at PortSwigger Research →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherPortSwigger Research
Canonical URLhttps://portswigger.net/research/css-the-bomb-inside-your-inbox
Publication timeSun, 09 Aug 2026 10:17:52 +0000
Retrieval time2026-08-09T11:00:42.851Z
Last seen2026-08-09T11:00:42.851Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster1lh0P93OV7AR · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

CSS:the bomb inside your inbox Gareth Heyes Researcher @garethheyes Published: Thursday, 6 August 2026 at 22:00 UTC Updated: Thursday, 6 August 2026 at 22:00 UTC Gareth Heyes - [email protected] - @garethheyesIt's quite common for webmail clients to render untrusted CSS in a trusted UI. They attempt to make this safe using CSS sanitization. In this paper I'm going to show you how to break out of trust boundaries, exfiltrate tokens, compromise 3rd party websites and even steal passwords.Table of contentsIntroductionAbusing allowed HTML/CSSAbusing HTML labels to perform UI actionsControlling AI browsers via emailAccount takeover from pasting into a draft emailExfiltrating tokens when CSP is blocking all external resourcesBypassing CSS sanitizationMaking external requestsSyntax…

Excerpt limited to ~120 words for fair-use compliance. The full article is at PortSwigger Research.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments