dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-6222

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Forminator plugin's `processRequest()` method in the admin module edit page performs only a nonce check before executing sensitive module-management actions (export, delete, clone, delete-entries, publish/draft, bulk operations) without verifying the user has the `manage_forminator_modules` capability. Since the nonce is globally embedded in the JavaScript on all Forminator admin pages—including those accessible to restricted users—and `processRequest()` runs during the `admin_menu` hook before WordPress enforces page-level capabilities, any authenticated user with subscriber-level or restricted Forminator role can manipulate forms, polls, and quizzes.

MitigationAdd a capability check for `manage_forminator_modules` before processing any action in `processRequest()`, and restrict nonce generation to users who possess the required capability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Forminator version
    In WordPress admin, go to Plugins > Forminator and note the installed version, or inspect the main plugin file (wp-content/plugins/forminator/forminator.php) for the 'Version' header
    Affected if Version matches the affected range (all versions prior to the patch containing capability verification)
  2. Locate the vulnerable processRequest method
    Inspect the file wp-content/plugins/forminator/library/modules/admin/module-edit.php (or similar path under admin) and search for the function processRequest()
    Affected if The method exists and performs nonce check without calling current_user_can('manage_forminator_modules') before executing actions
  3. Verify capability check is missing
    Within the processRequest() function, search for 'manage_forminator_modules' - if absent before action execution (export, delete, clone, delete-entries, publish/draft, bulk operations), the vulnerability exists
    Affected if No current_user_can('manage_forminator_modules') check found before sensitive operations
  4. Check user role configuration
    In WordPress admin, go to Users > Roles (or use a role editor plugin) and examine if subscriber-level users or custom 'Forminator' roles with limited capabilities exist
    Affected if Any authenticated user with subscriber role or restricted custom Forminator role can access Forminator admin pages
  5. Confirm nonce exposure to low-privilege users
    View the page source of any Forminator admin page while logged in as a restricted user; search for the nonce variable (wpApiSettings or similar)
    Affected if Nonce is present and accessible on admin pages viewable by subscriber-level or restricted users

Your environment is affected if Forminator is installed, the processRequest() method lacks a manage_forminator_modules capability check, and subscriber-level or restricted users can access Forminator admin pages where the nonce is exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add a capability check for `manage_forminator_modules` before processing any action in `processRequest()`, and restrict nonce generation to users who possess the required capability.

Recommended fix Moderate confidence

Forminator Forms plugin version 1.52.0 or later

  1. 1. Update the Forminator Forms plugin to the latest version available in the WordPress plugin repository (version 1.52.0 or later).
  2. 2. Navigate to WordPress Admin > Plugins > Forminator Forms.
  3. 3. If an update is available, click 'Update Now' to apply the security patch.
  4. 4. After updating, verify that the `manage_forminator_modules` capability check is now properly enforced for all sensitive module-management actions.
  5. 5. Confirm that users with restricted Forminator roles (Templates-only or Reports-only) can no longer access export, delete, clone, or publish/draft actions for forms, polls, or quizzes.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6222 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data