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.
CVE-2026-65051
Score 6.5 from GitHub Security Advisory published 2026-07-21. the CNA's CVSS baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.5
- EG Score
- 6.5(high)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity65% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 20.4%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 22, 2026
Advisory Details (3)
Auto-updated Jul 21, 2026Ninja Forms Server-Side Validation Bypass via Client-Controlled Field Metadata Merge in AJAX Submission Handler | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ninja-forms-server-side-validation-bypass-via-client-controlled-field-metadata-merge-in-ajax-submission-handlerNinja Forms – The Contact Form Builder That Grows With You – WordPress plugin | WordPress.org
https://wordpress.org/plugins/ninja-forms/changelog/Ninja Forms – The Contact Form Builder That Grows With You – WordPress plugin | WordPress.org
https://wordpress.org/plugins/ninja-forms/Vendor Advisories for CVE-2026-65051(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:22 UTCEG score recompute
- 2026-07-22 23:08 UTCEG score recompute
- 2026-07-22 23:08 UTCGHSA enrichment
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:29 UTCEG score recompute
- 2026-07-21 14:39 UTCEG score recompute
- 2026-07-21 14:37 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-65051?
When was CVE-2026-65051 disclosed?
Is CVE-2026-65051 actively exploited?
What is the CVSS score of CVE-2026-65051?
How do I remediate CVE-2026-65051?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65051
Is Your Infrastructure Affected by CVE-2026-65051?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.