Skip to main content
MediumHeadersOWASP A05:2021CWE-693

How to fix: CSP Allows Object/Embed Sources

CSP allows plugins via object-src.

Why it matters

Flash and other plugins can be exploited.

object-src should be 'none' unless plugins are required.

How to fix it

  1. 1Set object-src 'none' in CSP.

Code examples

Set object-src 'none' in CSP

JavaScript
// object-src controls Flash, Java applets, PDF embeds: all legacy plugins
// There is no legitimate reason to allow plugins in modern web apps:
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{
      key: "Content-Security-Policy",
      value: "default-src 'self'; object-src 'none'; plugin-types;"
    }]}];
  },
};

References

Detected automatically by VulnRadar. The check id is csp-object-src-unsafe, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is CSP Allows Object/Embed Sources?
VulnRadar rates this medium 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 csp-object-src-unsafe, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does CSP Allows Object/Embed Sources map to?
It maps to CWE-693. 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 csp allows object/embed sources

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: CSP Allows Object/Embed Sources | VulnRadar