dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-7291

HIGH · 7.2 CVSS v3.1 Published 2024-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 JetFormBuilder plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 3.3.4.1. This is due to improper restriction on user meta fields. This makes it possible for authenticated attackers, with administrator-level and above permissions, to register as super-admins on the sites configured as multi-sites.

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 JetFormBuilder plugin for WordPress versions up to 3.3.4.1 improperly restricts user meta field handling, allowing authenticated administrators on multi-site installations to escalate privileges to super-admin by manipulating user metadata during form submissions.

MitigationUpdate JetFormBuilder to version 3.3.4.2 or later. Until patched, audit all administrator and super-admin accounts for unauthorized changes and consider temporarily restricting admin-role user creation capabilities.

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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

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

  1. Identify JetFormBuilder version
    In WordPress admin, go to Plugins > Installed Plugins and locate JetFormBuilder. The version number is displayed below the plugin name. Alternatively, check the plugin file /wp-content/plugins/jetformbuilder/jet-form-builder.php and look for 'Version:' in the file header.
    Affected if The installed version is 3.3.4.1 or lower.
  2. Confirm WordPress multi-site mode
    In WordPress admin, go to Tools > Network Setup. If the page exists and shows network setup options, or if the site URL contains /wp-admin/network/, the installation is a multi-site network. Alternatively, check wp-config.php for 'MULTISITE' constant set to true.
    Affected if The WordPress installation is NOT a multi-site network - the vulnerability only applies to multi-site installations.
  3. Verify form submissions with user meta fields
    Review JetFormBuilder forms in the plugin settings. Look for any forms that include user-related fields, particularly those that may write to user metadata (fields with 'user_' or 'meta' in the name, or custom user fields). Check form actions for 'update_user' or similar meta update handlers.
    Affected if Forms exist that submit user metadata during form entries, and the plugin version is vulnerable.
  4. Audit super-admin account changes
    In multi-site WordPress, go to Network Admin > Super Admins. Compare the current super-admin list against known legitimate accounts. Check user metadata tables (wp_usermeta) for records where meta_key contains 'capabilities' or 'user_level' that were modified recently, especially by users who should not have super-admin privileges.
    Affected if Unauthorized changes to super-admin capabilities are found in user metadata, or unexpected accounts appear in the Super Admins list.

You are affected if JetFormBuilder version 3.3.4.1 or lower is installed on a WordPress multi-site network with forms that process user metadata submissions.

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

Update JetFormBuilder to version 3.3.4.2 or later. Until patched, audit all administrator and super-admin accounts for unauthorized changes and consider temporarily restricting admin-role user creation capabilities.

Recommended fix Moderate confidence

JetFormBuilder version 3.3.5 or later

  1. Update the JetFormBuilder plugin to version 3.3.5 or later through the WordPress plugin administration panel, or replace the plugin files with version 3.3.5 or newer
  2. Verify the update was successful by checking the plugin version in the WordPress admin Plugins section
  3. For WordPress multisite installations, verify that no unauthorized super-admin accounts have been created by reviewing the Super Admins list under Network Admin > Super Admins

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

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

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-7291 — 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-2024-7291 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