Skip to main content
MediumHeadersOWASP A05:2021CWE-693

How to fix: CSP Missing form-action Directive

The CSP header exists but does not contain a form-action directive to restrict form submission targets.

Why it matters

Forms can submit data to any URL, enabling form hijacking via injected <form> tags.

Without form-action, an attacker who injects HTML can add a <form> that submits to their server, exfiltrating data.

How to fix it

  1. 1Add 'form-action self' to your CSP.
  2. 2Explicitly list allowed form action targets.

Code examples

CSP

text
Content-Security-Policy: ... form-action 'self';

References

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

See every headers check

Questions

How severe is CSP Missing form-action Directive?
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-form-action-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does CSP Missing form-action Directive 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 missing form-action directive

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 Missing form-action Directive | VulnRadar