Forminator FormsWordPress extension · Wpmudev
CVE-2024-10402
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 · uneditedThe Forminator Forms – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in all versions up to, and including, 1.35.1. This makes it possible for authenticated attackers, with Contributor-level access and above, and permissions granted by an Administrator, to create new or edit existing forms, including updating the default registration role to Administrator on User Registration forms.
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 confidenceThe Forminator plugin for WordPress is vulnerable to broken access control due to a missing capability check on a function that handles form creation and editing. Authenticated users with Contributor-level permissions can create new forms, modify existing ones, and escalate privileges by changing the default registration role to Administrator on User Registration forms.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Forminator FormsWordPress extension
< 1.36.0CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Forminator plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Forminator Forms' or check the plugins directory for the Forminator plugin filesAffected if Forminator plugin is present on the site
-
Check installed Forminator versionNavigate to Plugins > Installed Plugins > Forminator Forms and read the version number displayed, or inspect the plugin header in /wp-content/plugins/forminator/readme.txt or the main plugin fileAffected if Version is below 1.36.0 (any version < 1.36.0 is vulnerable)
-
Identify User Registration formsGo to Forminator > Forms and review the list for any forms with 'User Registration' type. These are the forms that could be exploited for privilege escalationAffected if User Registration forms exist and the plugin version is vulnerable
-
Check default registration role settingIn Forminator settings or within User Registration form settings, locate the 'Default Role' or 'Set role' option to see what role is assigned to new usersAffected if Default role is set to Administrator (indicates the privilege escalation path is configured)
-
Review Contributor-level usersGo to Users in WordPress admin and filter or search for users with Contributor role. These users could exploit the vulnerability if Forminator is vulnerableAffected if There are Contributor-level users on the site and the vulnerable Forminator version is installed
A site is affected if Forminator plugin version is below 1.36.0 and there are User Registration forms with Administrator as the default role, allowing Contributor-level users to potentially escalate privileges.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.36.0
Update the Forminator plugin to version 1.35.2 or later which includes proper capability checks. Before updating, backup the site and test the update in a staging environment to ensure existing forms function correctly.
Forminator Forms 1.36.0
- Upgrade the Forminator Forms plugin to version 1.36.0 or higher via the WordPress plugin repository, plugin upload, or managed hosting dashboard
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Forminator Forms
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10402 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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