CVE-2026-6222 Missing authorization in Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Medium 5.3 Published Updated

Authenticated low-privilege users can export, delete, or modify Forminator modules due to missing capability checks in the admin module edit page.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-6222?

CVE-2026-6222 is a medium-severity missing authorization vulnerability in wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-862

Which versions are affected by CVE-2026-6222?

How do I fix CVE-2026-6222?

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-6222 being exploited?

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

Sources

Also known as GHSA-62w9-2w47-xvhj.

Is CVE-2026-6222 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free