Technical impact
The WebSub intent‑verification process echoes a supplied challenge value back to the subscriber. The protocol does not mandate safe response media typing or disabled MIME sniffing. As a result, when the subscriber returns the challenge as text/html or another executable MIME type, the browser will execute the reflected content in the subscriber’s origin. This leads to a reflected cross‑site scripting vulnerability that can access localStorage, sessionStorage, or other browser permissions held by that origin. The weakness is a classical unsanitized output flaw, classified as CWE‑79.
Affected Systems
This issue applies to implementations of the W3C WebSub recommendation, particularly those hosted by the W3C Social Web Working Group. No specific product versions are listed; the vulnerability may affect any WebSub implementation that mirrors the default challenge‑echo behavior described.
Risk and Exploitability
The CVSS score of 5.7 indicates a moderate severity. The EPSS score is not available and the vulnerability is not listed in CISA’s KEV catalog, suggesting no confirmed exploitation at this time. Nevertheless, the attack path is remote: an attacker can initiate a subscription and supply a crafted verification request. If the victim’s browser is directed to the malicious verification response or a same‑origin script resource, the reflected code can run. Safe media typing and the X‑Content‑Type‑Options: nosniff header are required to mitigate the described scenarios.