⛔ Access key required
This page is part of a security-research proof of concept (HackerOne #4086245) and only runs with a valid access key.

Nothing has been sent. Append ?k=<key> to the URL to run the demonstration.

Support-A-Creator — CORS Origin-Allowlist Bypass

HackerOne #4086245  ·  attacker page served from …  ·  target https://sac.epicgames.com
CORS … credentials … idle
🔑 Victim identity/api/get-profile
waiting…
💰 Financial recordread via CORS
waiting…
⚙️ Account objectsread via CORS
waiting…
✏️ Write operationno CSRF token
waiting…
📡 Live request feed 0 requests · 0 ok
📊 Impact summary
0credentialed reads returned data
0authenticated writes accepted
0enrolment-gated (would succeed for a real creator)
—write persisted on server
—original value restored
cross-origin read—
CSRF token sentnone
victim interactionnone required
* Access-Control-Allow-Origin is not a CORS-safelisted response header, so page script cannot print its literal value. A delivered cross-origin body is the proof the check passed; the literal headers are in the report's curl output (Parts A–E).
🛰️ Exfiltration feed→ evidence blob
waiting…

standby

The demonstration starts automatically…
Read-only except a reversible email-notification toggle on the signed-in account, which is written back to its original value before the run ends. No purchases, no anti-cheat interaction, no third-party content. Values that the account genuinely does not have are shown as —; nothing on this page is invented. X-Bug-Bounty cannot be sent from a browser — the API's preflight only allows x-xsrf-token,content-type — so the curl reproductions in the report carry it instead.