# CVE-2026-65051: Ninja Forms Server-Side Validation Bypass via Client-Controlled Field Metadata Merge in AJAX Submission Handler

> Unauthenticated attackers can bypass Ninja Forms validation by manipulating AJAX metadata, allowing submission of unverified content and triggering form actions.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-q572-6pwx-4p26

## What is CVE-2026-65051?

CVE-2026-65051 is a medium-severity vulnerability in Saturday Drive Ninja Forms, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ninja Forms WordPress plugin version 3.14.8 contains a client-side enforcement of server-side security vulnerability that allows unauthenticated attackers to bypass all form validation by merging attacker-controlled field metadata over server-loaded form definitions before validation runs. Attackers can craft a malicious AJAX submission overriding field types, removing required flags, and disabling CAPTCHA checks through the nopriv AJAX endpoint to trigger form actions such as email notifications and database storage with unverified, attacker-controlled content.

Weakness: CWE-602 (Client-Side Enforcement of Server-Side Security)

## Which versions are affected by CVE-2026-65051?


## How do I fix CVE-2026-65051?

No fix has been published for CVE-2026-65051 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-65051 being exploited?

There is no known exploitation of CVE-2026-65051 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-65051 and fix it if it is affected.

What it is: CVE-2026-65051 is a medium-severity vulnerability in Saturday Drive Ninja Forms, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65051 in the wild and no public exploit code.

Affected product: Saturday Drive Ninja Forms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-65051/ (Markdown: https://insights.sbomify.com/CVE-2026-65051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-65051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-65051
- OSV: https://osv.dev/vulnerability/CVE-2026-65051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-65051/
Summaries are generated and may contain mistakes; the official description above is the record.