HawkScan Test Info for HTTP to HTTPS Insecure Transition in Form Post

HTTP to HTTPS Insecure Transition in Form Post


Plugin Id: 10041 | CWE: 319


To remediate the vulnerability of “HTTP to HTTPS Insecure Transition in Form Post,” the following steps can be taken:

  1. Implement HTTPS for all pages: Ensure that all pages on the website are served over HTTPS instead of HTTP. This can be achieved by obtaining an SSL/TLS certificate and configuring the web server to use HTTPS.

  2. Redirect HTTP to HTTPS: Set up a redirect from HTTP to HTTPS to ensure that all requests are automatically redirected to the secure version of the website. This can be done by adding the following code to the web server configuration:

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  3. Verify HTTPS form submission: Implement server-side validation to ensure that form submissions are received only over HTTPS. This can be done by checking the protocol of the incoming request and rejecting any non-HTTPS submissions.

    if ($_SERVER['HTTPS'] !== 'on') {
        // Reject the form submission
        die('Form submission must be over HTTPS');


This vulnerability check identifies insecure HTTP pages that host HTTPS forms. The issue arises when an insecure HTTP page is susceptible to a Man-in-the-Middle (MITM) attack, allowing an attacker to intercept and modify the secure HTTPS form. This can lead to sensitive information being compromised or malicious actions being performed on behalf of the user.


The risks associated with the “HTTP to HTTPS Insecure Transition in Form Post” vulnerability include:

  • Data interception: An attacker can intercept the data submitted through the insecure HTTP page, potentially gaining access to sensitive information such as login credentials, personal details, or financial data.

  • Form manipulation: By hijacking the insecure HTTP page, an attacker can modify the secure HTTPS form, altering the intended behavior or injecting malicious code. This can lead to unauthorized actions being performed on behalf of the user or the submission of malicious data.

  • Spoofing: An attacker can impersonate the secure HTTPS form by replacing it with a malicious form that appears legitimate. This can trick users into submitting sensitive information to the attacker, unknowingly compromising their data.

It is crucial to address this vulnerability to ensure the secure transmission of data and protect users from potential attacks.