Skip to main content
MediumContent

How to fix: JSONP Endpoint Detected

JSONP callback parameter found.

Why it matters

JSONP can leak data cross-origin.

JSONP bypasses same-origin policy by design.

How to fix it

  1. 1Replace JSONP with CORS for cross-origin requests.

Code examples

Replace JSONP with CORS

TypeScript
// JSONP is dangerous: the callback parameter executes arbitrary code
// BAD: /api/data?callback=someFunction

// GOOD: use CORS instead
return new Response(JSON.stringify(data), {
  headers: {
    "Content-Type": "application/json",
    "Access-Control-Allow-Origin": "https://trusted-partner.com",
  },
});

// JSONP endpoints cannot be protected with CSRF tokens or SameSite cookies

References

Detected automatically by VulnRadar. The check id is jsonp-endpoint, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is JSONP Endpoint Detected?
VulnRadar rates this medium severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id jsonp-endpoint, which stays the same between runs so you can filter, diff, or gate CI on it.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for jsonp endpoint detected

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: JSONP Endpoint Detected | VulnRadar