Skip to main content
CriticalCodeOWASP A02:2021CWE-319

How to fix: Form Submits Data Over Insecure HTTP

An HTTPS page contains a form that submits data to an HTTP endpoint.

Why it matters

User credentials and form inputs are transmitted in plaintext.

When a secure page sends form data to an insecure endpoint, all submitted data travels unencrypted.

How to fix it

  1. 1Change all form action URLs to use HTTPS.
  2. 2Use relative URLs so forms inherit the page protocol.
  3. 3Implement HSTS.

Code examples

Fix

HTML
<!-- BAD -->
<form action="http://example.com/login" method="POST">
<!-- GOOD -->
<form action="/login" method="POST">

References

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

See every code check

Questions

How severe is Form Submits Data Over Insecure HTTP?
VulnRadar rates this critical severity in the code 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 insecure-form-submission, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Form Submits Data Over Insecure 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.

Propose a checkHow a check is built

Scan your own site for form submits data over insecure http

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: Form Submits Data Over Insecure HTTP | VulnRadar