Ninja Forms WordPress plugin version 3.14.8 and prior contains a missing authorization vulnerability in the render callback of the ninja-forms/submissions-table Gutenberg block that allows authenticated attackers with Author-level privileges to expose stored form submissions to unauthenticated visitors by embedding the block with an arbitrary formID on a published post. Attackers can retrieve the signed bearer token injected into every page visitor's browser via wp_localize_script and use it against the REST API submissions endpoint to access all saved form submission field values, including sensitive personally identifiable information such as names, email addresses, and phone numbers.
CVE-2026-65050
MEDIUMPre-NVD 6.56.5—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-21. the CNA's CVSS baseline 6.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cna:vulncheck, epss, ghsa
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0
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
- 23.3%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 23, 2026
Advisory Details (3)
Auto-updated Jul 21, 2026⚠️ Active exploitation confirmed. No patch confirmed yet.
generic
Ninja Forms Missing Authorization in submissions-table Gutenberg Block Discloses Form Submissions to Unauthenticated Visitors | Advisories | VulnCheck
https://www.vulncheck.com/advisories/ninja-forms-missing-authorization-in-submissions-table-gutenberg-block-discloses-form-submissions-to-unauthenticated-visitorsgeneric🔴 Active Exploitation
Ninja Forms – The Contact Form Builder That Grows With You – WordPress plugin | WordPress.org
https://wordpress.org/plugins/ninja-forms/changelog/generic🔴 Active Exploitation
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-65050(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 10× in last 7d / 10× 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 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 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
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-65050?
CVE-2026-65050 is a medium vulnerability published on July 21, 2026. Ninja Forms WordPress plugin version 3.14.8 and prior contains a missing authorization vulnerability in the render callback of the ninja-forms/submissions-table Gutenberg block that allows authenticated attackers with Author-level privileges to expose stored form submissions to unauthenticated…
When was CVE-2026-65050 disclosed?
CVE-2026-65050 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65050 actively exploited?
CVE-2026-65050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-65050?
CVE-2026-65050 has a CVSS v4.0 base score of 6.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-65050?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65050, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65050
Is Your Infrastructure Affected by CVE-2026-65050?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.