How to fix: Form submits data over unencrypted HTTP
An HTML form uses an HTTP (not HTTPS) action URL, transmitting form data in plaintext.
Why it matters
Form data submitted over HTTP is visible to any network observer, exposing passwords, personal data, payment information, or authentication tokens to interception.
All form actions must use HTTPS URLs.
How to fix it
- 1Change the form action from http:// to https://
- 2Enable HSTS to prevent HTTP downgrades
- 3Audit all forms to verify action URLs use HTTPS
Code examples
Correct form action
<!-- BAD: <form action="http://example.com/submit"> -->
<!-- GOOD: -->
<form action="https://example.com/submit" method="POST">
<!-- Always use HTTPS for form submissions -->
</form>References
Detected automatically by VulnRadar. The check id is form-action-http, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Form submits data over unencrypted HTTP?
- VulnRadar rates this high 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 form-action-http, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Form submits data over unencrypted HTTP map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02: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.