Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/web-corsWeb and bug bounty

web-cors

⁨Exploit CORS misconfiguration to read cross-origin responses (data theft). Load when an API reflects Origin into Access-Control-Allow-Origin, allows credentials cross-origin, or trusts null/subdomains. Signals: ACAO reflects your Origin, ACAC: true, `Origin`-dependent responses.⁩

v2026.10.14-ee0e0c54 installs+4 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/web-cors

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
hmG9O+K/YJ…3tB2VFAw==The CLI checks the SHA-256 and the signature before it writes a file.
Package515c0fa8…efe52445
515c0fa83c4b…64b5efe524451 file · ⁦1.1 KB⁩
ScanLow1 finding
  • Links to outside domains
See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/web/web-cors@ee0e0c5

When it applies

An endpoint returns sensitive data and sets CORS headers that let an attacker origin read the response with the victim's credentials.

Why it works

CORS lets a server opt-in to cross-origin reads. If it reflects the request Origin into Access-Control-Allow-Origin and sets Access-Control-Allow-Credentials: true, any site can make the victim's browser send an authenticated request and read the response — cross-origin data theft.

Method

  1. Probe: send requests with Origin: https://evil.com and inspect response headers. Vulnerable if ACAO echoes your origin (or null) AND ACAC is true.
  2. Test weak allowlists: Origin: https://evil.com vs https://sub.target.com.evil.com, https://targetevil.com, null (via sandboxed iframe), and non-TLS variants — many regexes are sloppy.
  3. Exploit: host JS on your origin that fetch(url, {credentials:'include'}) the sensitive endpoint and exfils the response to you; load it as the victim.

Gotchas

  • ACAO: * without credentials can't read authed data — only origin-reflection + ACAC:true (or a same-site secret) is impactful.
  • null origin is reachable from sandboxed iframes/data: URLs — a real bypass, not theoretical.
  • Prove it reads sensitive data (tokens, PII); reflecting on a public endpoint is informational.

Verify success

Your attacker-origin page reads a victim-authenticated response it should not be able to (e.g. the victim's API key/PII exfiltrated to your server).

References

PortSwigger CORS labs; OWASP CORS guidance.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5515c0fa8Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login