How to fix: Form action points to an insecure or external URL
A form action attribute uses plain HTTP, or points to a domain that is neither your own site nor a known form/payment processor, risking submission to an untrusted destination. Forms posting to your own site, or to a processor whose documented embed code requires a cross-origin action (Stripe, PayPal, Mailchimp, HubSpot, Jotform, Salesforce Web-to-Lead, and similar), are not reported.
Why it matters
Forms that submit to HTTP URLs expose credentials in transit. Forms targeting external domains may submit user data to attacker-controlled servers, a common phishing vector.
Form actions should always point to HTTPS endpoints on your own domain.
How to fix it
- 1Change all form actions to HTTPS URLs
- 2Ensure the action domain is your own, not a third-party or user-controlled value
- 3Validate the action URL server-side if it is dynamically generated
Code examples
Restrict form action to known paths
<!-- Unsafe: accepts any action value from user input -->
<form action="<?= $_GET['redirect'] ?>">...</form>
<!-- Safe: hardcoded action -->
<form action="/api/v1/login" method="post">...</form>References
Detected automatically by VulnRadar. The check id is open-form-action, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Form action points to an insecure or external URL?
- VulnRadar rates this medium severity in the content 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 open-form-action, which stays the same between runs so you can filter, diff, or gate CI on it.
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.