dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2023-37866

HIGH · 7.2 CVSS v3.1 Published 2024-05-17
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
Improper Privilege Management vulnerability in Crocoblock JetFormBuilder allows Privilege Escalation.This issue affects JetFormBuilder: from n/a through 3.0.8.

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 · moderate confidence

Improper Privilege Management vulnerability in the Crocoblock JetFormBuilder WordPress plugin allows a user with lower privileges to escalate their access level beyond what should be permitted. The vulnerability exists in versions through 3.0.8 and stems from insufficient permission checks within the form handling logic.

MitigationUpdate JetFormBuilder to the latest version (3.0.9 or later) which contains the privilege management fix. Restrict administrative access to the plugin settings until the update is applied.

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. Confirm JetFormBuilder plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/jetformbuilder directory exists, or run: wp plugin list --name=jetformbuilder
    Affected if The JetFormBuilder plugin is present on the WordPress site
  2. Check installed JetFormBuilder version
    In WordPress admin, go to Plugins > Installed Plugins and find the JetFormBuilder version number, or check the plugin header in /wp-content/plugins/jetformbuilder/jetformbuilder.php, or run: wp plugin get jetformbuilder --format=json
    Affected if The installed version is 3.0.8 or earlier (versions through 3.0.8 are affected)
  3. Verify privilege escalation condition exists
    Navigate to Users in WordPress admin and review user roles. The vulnerability allows users with subscriber, contributor, or author roles to escalate privileges. Check if any such lower-privileged user accounts exist on the site.
    Affected if There are users with roles below Administrator (subscriber, contributor, author) who have access to form functionality
  4. Check if JetFormBuilder forms are in use
    Navigate to JetFormBuilder > Forms in the WordPress admin panel, or check the wp_posts table for post_type = 'jet-form-builder' entries, or inspect the database for forms created with this plugin
    Affected if Active forms exist and lower-privileged users have access to submit or manage them

The site is affected if JetFormBuilder version 3.0.8 or earlier is installed AND there are non-administrator users who can access the plugin's form functionality.

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 the latest version (3.0.9 or later) which contains the privilege management fix. Restrict administrative access to the plugin settings until the update is applied.

Recommended fix Moderate confidence

JetFormBuilder version 3.0.9 or later (latest stable release)

  1. Check the current version of JetFormBuilder plugin installed on the WordPress site
  2. Access the WordPress admin dashboard and navigate to Plugins > Installed Plugins
  3. Locate JetFormBuilder and verify the current version number
  4. Navigate to Plugins > Add New > Upload Plugin or use WordPress update mechanism to update JetFormBuilder to the latest available version
  5. After updating, verify the new version is installed (should be version 3.0.9 or later)
  6. Test that forms still function correctly after the update
  7. Ensure WordPress core and other plugins are also kept up to date
Caveat Review JetFormBuilder changelog for any breaking changes between your current version and the new version before updating

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-2023-37866 — 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-2023-37866 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