Skip to main content

How to fix: formnovalidate attribute on submit button

A submit button with formnovalidate bypasses HTML5 input constraints (required, pattern, type=email). This is also the standard, expected attribute for 'save draft'/'skip'/'cancel' buttons in multi-step forms, so its presence alone does not confirm a bypassable validation gap; it's a reminder that server-side validation must catch what the browser doesn't.

Why it matters

Low on its own. Always validate on the server; never rely on browser-side form validation alone.

A submit button with formnovalidate bypasses HTML5 input constraints (required, pattern, type=email). Server-side validation must catch this.

How to fix it

  1. 1Always validate on the server; never rely on browser-side form validation alone

Code examples

Always validate server-side regardless of formnovalidate

TypeScript
// formnovalidate only skips browser-level validation (for save/draft buttons)
// ALWAYS validate server-side regardless

export async function POST(req: Request) {
  const data = await req.json();
  // Server-side validation is mandatory
  if (!data.email || !/^[^@]+@[^@]+\.[^@]+$/.test(data.email)) {
    return Response.json({ error: "Invalid email" }, { status: 400 });
  }
  // process
}

References

Detected automatically by VulnRadar. The check id is form-formnovalidate-bypass, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is formnovalidate attribute on submit button?
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-formnovalidate-bypass, 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.

Propose a checkHow a check is built

Scan your own site for formnovalidate attribute on submit button

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

formnovalidate attribute on submit button fix | VulnRadar