The Forminator Forms plugin for WordPress is vulnerable to Missing Authorization in versions up to and including 1.51.1. This is due to the processRequest() method in Forminator_Admin_Module_Edit_Page (admin/abstracts/class-admin-module-edit-page.php) dispatching sensitive module-management actions — including export, delete, clone, delete-entries, publish/draft, and bulk variants — after only a nonce check, without ever verifying that the current user holds the manage_forminator_modules capability. The nonce used (forminator_form_request) is unconditionally embedded in the global forminatorData JavaScript object and localized on every Forminator admin page, including Templates and Reports pages accessible to users who explicitly lack module-management permissions. Because processRequest() is invoked during the admin_menu action hook — which fires before WordPress enforces page-level capability checks — a user whose Forminator role is restricted to Templates or Reports can craft a valid POST request targeting any published module and successfully trigger the vulnerable actions. This makes it possible for authenticated attackers with subscriber-level access (or any custom low-privilege Forminator role) to export the complete internal configuration of arbitrary forms/polls/quizzes (including notification routing, integration credentials, and conditional logic), delete modules, delete all submissions/votes, clone modules, or bulk-change publish/draft status.
CVE-2026-6222
“—” beside the score: it is equal to NVD's CVSS score.
Score 5.3 from GitHub Security Advisory published 2026-05-07. NVD baseline CVSS 5.3; sources differ by 0.0.
Also known asEUVD-2026-28235 (ENISA EUVD) · GHSA-62w9-2w47-xvhj (GitHub Security Advisories)Source: ENISA EUVD
- Lower severity and no public exploit yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
The CVE record's CNA (Wordfence) lists wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder versions up to and including 1.51.1 as affected. No release containing a fix is confirmed on record.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 24EG Risk 24/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix. - EPSS PROB
- 0.4%
- EPSS %ILE
- 36th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
May 7, 2026
Last Modified
May 7, 2026
References (8)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/tags/1.51.1/admin/abstracts/class-admin-module-edit-page.php#L1008
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/tags/1.51.1/admin/abstracts/class-admin-module-edit-page.php#L951
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/tags/1.51.1/admin/classes/class-admin-data.php#L141
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/tags/1.52/admin/abstracts/class-admin-module-edit-page.php#L988
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/trunk/admin/abstracts/class-admin-module-edit-page.php#L1008
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/trunk/admin/abstracts/class-admin-module-edit-page.php#L951
- security@wordfencehttps://plugins.trac.wordpress.org/browser/forminator/trunk/admin/classes/class-admin-data.php#L141
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/e860aa70-b8ef-4b2a-a035-b01efce30a79?source=cve
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 37× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 98 of 227 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 129 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 14:14 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-22 19:53 UTCEG score recompute
- 2026-10-22 19:53 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-18 03:24 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-12 15:50 UTCEG score recompute
- 2026-10-11 19:34 UTCEG score recompute
- 2026-10-11 16:49 UTCEG score recompute
Show 73 moreShow fewer
- 2026-10-11 14:11 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-23 19:40 UTCEG score recompute
- 2026-08-23 19:40 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-17 12:49 UTCEG score recompute
- 2026-08-17 12:49 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-16 04:47 UTCEG score recompute
- 2026-08-16 04:47 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-15 01:21 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-14 03:20 UTCEG score recompute
- 2026-08-14 03:20 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-12 21:28 UTCEG score recompute
- 2026-08-12 21:28 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-11 23:27 UTCEG score recompute
- 2026-08-11 23:27 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-11 01:27 UTCEG score recompute
- 2026-08-11 01:27 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-10 00:31 UTCEG score recompute
- 2026-08-10 00:31 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-09 02:30 UTCEG score recompute
- 2026-08-09 02:30 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-08-07 18:17 UTCEG score recompute
- 2026-08-07 18:17 UTCGHSA enrichmentGHSA-62w9-2w47-xvhj · GitHub CVSS 5.3
- 2026-08-06 20:16 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-6222?
When was the CVE record for CVE-2026-6222 published?
Is CVE-2026-6222 actively exploited?
What is the CVSS score of CVE-2026-6222?
How do I remediate CVE-2026-6222?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6222
Is Your Infrastructure Affected by CVE-2026-6222?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.