Reflected script execution in WebSub intent-verification challenges
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Cross-site scripting
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-79.
Summary
The W3C WebSub recommendation REC-websub-20180123 does not require subscribers to use safe media typing or disable MIME sniffing when echoing the hub.challenge value during intent verification (CWE-79). An attacker can start a subscription and redirect a victim's browser to a crafted verification request containing HTML or JavaScript. Subscribers that return the challenge as text/html run the reflected content in their origin, where it can read localStorage, sessionStorage and granted browser permissions using the victim's session.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Description from the CNA
WebSub is a W3C recommendation produced by the Social Web Working Group. In recommendation REC-websub-20180123, the intent-verification protocol requires a subscriber to echo the `hub.challenge` value, also exposed as `hub_challenge` by some frameworks, but does not require safe response media typing or disabled MIME sniffing. An attacker can initiate a subscription to obtain a callback URL and redirect a victim browser to a crafted verification request containing HTML or JavaScript. Subscribers that return the challenge as `text/html` can execute the reflected content in the subscriber origin, using a victim's existing session to read private data or perform actions, exposing `localStorage` or `sessionStorage` and browser permissions granted to that origin. An alternative uses the verification response as an attacker-controlled same-origin script resource to bypass `script-src 'self'`; this can remain possible with `application/octet-stream` when MIME sniffing is allowed. Safe media typing and `X-Content-Type-Options: nosniff` are both needed to address the described scenarios. WebSub Rocks demonstrated reflection, but the advisory does not establish practical impact on that demonstration site.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
The sources list no fixed version for WebSub. Use safe media typing for the challenge response and send X-Content-Type-Options: nosniff, which the advisory says are both needed to address the described scenarios.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
Timeline
- 2026-10-27 Threatist record created from CVE-2026-50571
- 2026-10-28 CISA SSVC decision points changed
- 2026-10-28 Priority changed: MEDIUM → LOW
References
More w3c vulnerabilities
- TI-2025-01533 XML external entity injection in w3c CSS Validator CVSS 4.0HIGH 8.4
- TI-2008-05027 Multiple stack-based buffer overflows in W3C Amaya Web Browser 10.0.1 allow remote… CVSS 2.0HIGH 10.0
- TI-2008-05701 Multiple buffer overflows in the CheckUniqueName function in W3C Amaya Web Browser… CVSS 2.0HIGH 10.0
- TI-2006-01845 Multiple buffer overflows in World Wide Web Consortium (W3C) Amaya 9.4, and possibly… CVSS 2.0HIGH 7.6
- TI-2000-00079 The W3C CERN httpd HTTP server allows remote attackers to determine the real pathnames of… CVSS 2.0HIGH 7.5
- TI-2002-01025 Cross-site scripting (XSS) vulnerability in W3C Jigsaw Proxy Server before 2.2.1 allows… CVSS 2.0MEDIUM 6.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences