How to fix: Form action uses javascript: scheme
A <form action="javascript:..."> executes JavaScript on submit and is a classic XSS vector if the action is partially attacker-controlled.
Why it matters
Replace action="javascript:..." with action="/endpoint" and handle submit via JS or server
A <form action="javascript:..."> executes JavaScript on submit and is a classic XSS vector if the action is partially attacker-controlled.
How to fix it
- 1Replace action="javascript:..." with action="/endpoint" and handle submit via JS or server
Code examples
Never use javascript: in form action
<!-- BAD: form action with javascript: scheme executes arbitrary JS -->
<!-- <form action="javascript:void(0)" onsubmit="handle()"> -->
<!-- GOOD: use a real action URL or submit via JavaScript -->
<form id="myForm" action="/api/submit" method="POST">
<!-- ... -->
</form>
<script>
document.getElementById("myForm").addEventListener("submit", async (e) => {
e.preventDefault();
await fetch("/api/submit", { method: "POST", body: new FormData(e.target) });
});
</script>References
Detected automatically by VulnRadar. The check id is form-action-javascript-scheme, 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 uses javascript: scheme?
- VulnRadar rates this high 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 form-action-javascript-scheme, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Form action uses javascript: scheme map to?
- It maps to CWE-79. In the OWASP Top 10 it falls under A03: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.