CyberKit

Cross-Origin Resource Sharing

Also called CORS.

Headers that relax the same-origin policy for chosen origins.

What it is

A browser mechanism that lets a server use response headers to permit specific other origins to read its responses, selectively loosening the same-origin policy for legitimate cross-origin requests.

Why it matters

Misconfigured CORS (reflecting any origin or allowing credentials too broadly) can expose sensitive data to attacker sites, making overly permissive policies a frequent finding in web assessments.

In practice

An API that reflects whatever Origin it receives and allows credentials, letting any site read a user's data.

What to look for

  • Access-Control-Allow-Origin reflecting any origin.
  • Credentials allowed with wildcard origins.
  • Trusted origins that include null.

Common mistake

Reflecting the Origin header. It turns CORS into an open door.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

  • Content Security Policy: A header that restricts which sources a page may load and run.
  • API Security: Protecting application programming interfaces from abuse and data exposure.
  • Security Headers: HTTP response headers that harden the browser's handling of a site.

Sources