Home / Core Health / Fix forms that submit over plain HTTP
Content & Files · Scan Check Guide

Fix forms that submit over plain HTTP

15 min Impact: high Effort: low ✓ Scan-verified — no manual checkbox

A form on an HTTPS page that submits its data to a plain HTTP endpoint sends everything the visitor typed — including passwords or payment details — over an unencrypted connection, even though the page itself looked secure with a padlock icon.

A form whose action posts to http:// instead of https:// sends whatever the visitor typed — including passwords — across the network in plain text, readable by anyone on the same network.

The full picture

Forms submitting over plain HTTP, even on a site that's otherwise properly configured for HTTPS, expose whatever data a visitor enters into that specific form to the same interception and tampering risks that comprehensive HTTPS enforcement elsewhere on your site is meant to eliminate — this represents a specific, often-overlooked gap in otherwise solid HTTPS implementation.

This vulnerability commonly occurs through legacy form configurations or third-party form-handling integrations that were never updated when the broader site transitioned to HTTPS — the surrounding page might load securely, but the specific form action attribute still points to an HTTP endpoint, creating this isolated but genuinely serious gap in an otherwise secure page.

The genuine risk here scales with what information the specific form collects — a contact form collecting only a name and general message represents lower risk than a form collecting passwords, payment information, or other genuinely sensitive data, though any form submission over HTTP represents a real, avoidable security gap worth closing regardless of the specific data involved.

Remediation requires identifying every form on your site and verifying its actual submission destination uses HTTPS, then correcting any instances still pointing to HTTP endpoints — this check specifically catches gaps that broader site-wide HTTPS verification might miss if it only checks page-loading behavior without specifically verifying form submission destinations.

How to fix it

  1. 1
    Check every form's action attribute
    Look at each <form> tag's action URL — confirm it starts with https://, not http://.
  2. 2
    Fix any found
    Update the form action to point to the https:// version of the same endpoint.
  3. 3
    Check forms that submit to third-party services too
    Newsletter signups, payment forms, and embedded widgets sometimes submit to an external service — confirm that endpoint is also HTTPS.

Common mistakes

How you'll know it's done

Every form on the site submits its data to an HTTPS endpoint.

H.I.V.E. checks this automatically

Fix it, then re-scan — the check confirms itself. No manual checkbox, the scan is the truth.

Run this check in H.I.V.E. →