dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-54196

MEDIUM · 6.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Subscriber Privilege Escalation in JetFormBuilder <= 3.6.1 versions.

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

This is a privilege escalation vulnerability in the JetFormBuilder WordPress plugin affecting versions 3.6.1 and below. The vulnerability allows users with the Subscriber role to elevate their privileges, likely through improper capability checks in the plugin's form handling or administrative functions.

MitigationUpdate JetFormBuilder to the latest version once available. If a patch is not available, consider restricting subscriber registration or implementing additional access controls at the web application firewall level.

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

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

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
    Navigate to WordPress admin dashboard > Plugins page and look for JetFormBuilder in the list of installed plugins
    Affected if JetFormBuilder appears in the installed plugins list
  2. Check installed JetFormBuilder version
    Click on JetFormBuilder in the plugins list to view version details, or check the plugin file header in wp-content/plugins/jetformbuilder/jetformbuilder.php for the 'Version' comment
    Affected if The reported version is 3.6.1 or any version below 3.6.1 (e.g., 3.6.0, 3.5.x, etc.)
  3. Verify if Subscriber role users exist
    In WordPress admin, go to Users > All Users and filter or check for users with the Subscriber role
    Affected if There is at least one user account assigned the Subscriber role
  4. Check if JetFormBuilder forms are publicly accessible
    Inspect JetFormBuilder form shortcodes or blocks on any published page, or check the plugin settings under JetFormBuilder > Forms to see if forms allow submissions from non-authenticated or Subscriber-level users
    Affected if Forms are configured to accept submissions from users with Subscriber role or lower without additional capability verification

You are affected if JetFormBuilder version 3.6.1 or below is installed AND Subscriber role accounts exist in your WordPress environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetFormBuilder to the latest version once available. If a patch is not available, consider restricting subscriber registration or implementing additional access controls at the web application firewall level.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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