How to fix: Form action uses mailto: scheme
A <form action="mailto:..."> opens the user's mail client, leaks the recipient address, and is unreliable for data submission.
Why it matters
Use a server endpoint or contact form instead of mailto: for form submission
A <form action="mailto:..."> opens the user's mail client, leaks the recipient address, and is unreliable for data submission.
How to fix it
- 1Use a server endpoint or contact form instead of mailto: for form submission
Code examples
Replace mailto: form actions with a server-side form handler
// BAD: <form action="mailto:[email protected]">, exposes email, client-dependent
// GOOD: handle form submission server-side
export async function POST(req: Request) {
const formData = await req.formData();
const name = formData.get("name") as string;
const message = formData.get("message") as string;
// Send email server-side with your email service
await sendEmail({ to: process.env.CONTACT_EMAIL!, subject: `Contact: ${name}`, body: message });
return Response.json({ success: true });
}References
Detected automatically by VulnRadar. The check id is form-action-mailto-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 mailto: scheme?
- VulnRadar rates this low 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-mailto-scheme, 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.