dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-64384

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Missing Authorization vulnerability in jetmonsters JetFormBuilder jetformbuilder allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects JetFormBuilder: from n/a through <= 3.5.3.

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

JetFormBuilder plugin versions up to 3.5.3 contain a missing authorization vulnerability where certain functionality fails to properly validate user permissions before executing sensitive operations. This broken access control allows authenticated attackers to access or modify data beyond their intended privileges due to incorrectly configured security levels.

MitigationUpdate JetFormBuilder to the latest patched version (3.5.4 or higher). If no update is available, audit the plugin's access control logic and implement proper capability checks on all sensitive actions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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. Locate JetFormBuilder plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find JetFormBuilder, and read the version number from the plugin row. Alternatively, inspect /wp-content/plugins/jetformbuilder/includes/version.php or the plugin's main header comment.
    Affected if The displayed version is 3.5.3 or any version lower than 3.5.3
  2. Confirm plugin is active
    Verify the JetFormBuilder plugin status shows as 'Active' in the WordPress plugins list.
    Affected if Plugin is active and version is 3.5.3 or lower; inactive plugins with vulnerable versions still present a risk if activated later
  3. Identify user roles with form management access
    Navigate to JetFormBuilder settings or form editor and review which user roles (Administrator, Editor, Author, etc.) have permission to create or edit forms. Check WordPress Users > Roles to see custom role capabilities related to JetFormBuilder.
    Affected if Non-administrator roles (Editor, Author, Contributor, or custom roles) have elevated form creation or modification capabilities without documented capability verification steps
  4. Audit access control on sensitive actions
    If you have access to the server, inspect jetformbuilder includes/ classes for action-handler methods lacking current_user_can() or capability checks before executing data modifications.
    Affected if Code review reveals action handlers that execute without permission validation, indicating the broken access control is present

You are affected if JetFormBuilder version 3.5.3 or lower is installed and active, as the missing authorization vulnerability exists in this version range.

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 patched version (3.5.4 or higher). If no update is available, audit the plugin's access control logic and implement proper capability checks on all sensitive actions.

Recommended fix Moderate confidence

Update JetFormBuilder to the latest available version (version after 3.5.3)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate JetFormBuilder in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is functioning correctly on your site
  6. 6. Test forms to ensure they work as expected after the update
Caveat Review the plugin changelog for any breaking changes between your current version and the new version before updating on production sites

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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