Skip to content

HackerOne · disclosed report #321

CSP not consistently applied

How it was found, in CyberSIXT's words · 34 votes

This analysis is CyberSIXT's own summary of the public report, written by a model and checked automatically. It may be wrong: the researcher's report is the source.

Read the researcher's report

Read the researcher's report on HackerOne

The report alleges that some responses omit Content Security Policy headers for unsupported browsers, and that a CDN may cache those responses. It does not describe an exploit or demonstrate that this enables cross-site scripting.

How it was found

  1. The researcher noticed inconsistent CSP headers across browser responses.
  2. They observed or suspected that a response without CSP could be cached by the CDN.
  3. They linked this behavior to increased XSS risk, without reporting a confirming test.
Access needed
No account
User interaction
Not clear
Whose object
No object involved
Boundary crossed
No decisive security boundary crossing is demonstrated.
Root cause
CSP header delivery may vary by browser, allowing a response without the policy to be cached and served more broadly.
Impact
Cached responses without CSP could reduce a defense-in-depth barrier against XSS, but no exploitable XSS or affected users are established.
Components
HTTP response headers, content security policy, CDN cache
Confidence
low

This analysis is CyberSIXT's own summary of the public report, written by a model and checked automatically. It may be wrong: the researcher's report is the source. Written 2026-11-15. Ask for a correction or removal.

Similar findings, side by side
ReportAccessWhose objectBoundary crossed
[Grab Android/iOS] Insecure deeplink leads to sensitive information disclosureNo accountThe attacker's ownA crafted deeplink caused the app's privileged webview to disclose its user's data to attacker-controlled content.
Email templates XSS by filterXSS bypassA user accountAnother user'sA crafted template preview crossed into another user's authenticated context, enabling access to private content and account credentials.
XSS vulnerable parameter in a location hashNo accountNo object involvedA crafted link could cause script execution in a victim’s site context.
[accounts.reddit.com] Redirect parameter allows for XSSNo accountNo object involvedA crafted redirect destination caused script execution in the account site’s browser context.
yelp.com XSS ATO (via login keylogger, link Google account)No accountAnother user'sA crafted link causes script to run in a victim’s Yelp session and link an attacker-controlled identity to the victim’s account.
XSS at jamfpro.shopifycloud.comNo accountNo object involvedA crafted link caused attacker-controlled script to execute in the application origin.
Stored XSS in developer.uber.comA user accountNo object involvedA contributor’s stored suggestion executes in an administrator’s dashboard context.
[www.zomato.com] Blind XSS on one of the Admin DashboardA user accountThe attacker's ownCustomer-submitted order content executed in an administrator's browser.
Account Takeover in Periscope TVNo accountAnother user'sOAuth authorization data for a victim was sent to an attacker-controlled destination.
XSS and cache poisoning via upload.twitter.com on ton.twitter.comA user accountAnother tenant'sA signed upload made an attacker-controlled file viewable by another user in the target origin.
XSS at https://exchangemarketplace.com/blogsearchNo accountNo object involvedUntrusted search input was interpreted as script in the site's page.
xss on https://www.rockstargames.com/GTAOnline/jp/screens/No accountNo object involvedUntrusted path content was treated as executable script in a visitor's browser.
Program
HackerOne
Status
Valid
Bounty
None stated
Weakness as filed
Cross-site Scripting (XSS) - Generic
Disclosed
2013
Upvotes
34

Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.