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

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

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-62w9-2w47-xvhj

## 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 (Missing Authorization)

## 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.

## Is CVE-2026-6222 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6222 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-6222 in the wild and no public exploit code.

Affected product: wpmudev Forminator Forms – Contact Form, Payment Form & Custom Form Builder. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6222/ (Markdown: https://insights.sbomify.com/CVE-2026-6222/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6222
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6222
- OSV: https://osv.dev/vulnerability/CVE-2026-6222

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6222/
Summaries are generated and may contain mistakes; the official description above is the record.