Skip to main content
LowHeadersOWASP A05:2021CWE-942

How to fix: Missing X-Permitted-Cross-Domain-Policies header

The server does not send X-Permitted-Cross-Domain-Policies: none, so legacy plugins (Adobe Flash, Acrobat Reader) fall back to permissive cross-domain policy discovery.

Why it matters

Without this header set to 'none', a legacy plugin on an older browser may load a permissive crossdomain.xml from this origin (or a parent path) and grant cross-domain data access it shouldn't have.

X-Permitted-Cross-Domain-Policies controls whether Adobe Flash and Acrobat treat this domain as willing to share data with other domains via crossdomain.xml. Modern browsers have dropped Flash, but the header is still checked by security scanners and costs nothing to set.

How to fix it

  1. 1Add X-Permitted-Cross-Domain-Policies: none to all responses.
  2. 2If you deliberately serve a crossdomain.xml for a legacy integration, use 'master-only' instead of 'none' so only that top-level file is honored.

Code examples

Next.js

JavaScript
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "X-Permitted-Cross-Domain-Policies", value: "none" }] }];
  },
};

Nginx

nginx
add_header X-Permitted-Cross-Domain-Policies "none" always;

References

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

See every headers check

Questions

How severe is Missing X-Permitted-Cross-Domain-Policies header?
VulnRadar rates this low severity in the headers 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 xpcdp-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Missing X-Permitted-Cross-Domain-Policies header map to?
It maps to CWE-942. In the OWASP Top 10 it falls under A05:2021.

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 missing x-permitted-cross-domain-policies header

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

Missing X-Permitted-Cross-Domain-Policies header | VulnRadar