dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-56008

HIGH · 8.8 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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
Contributor Privilege Escalation in Fusion Builder <= 3.15.4 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 · moderate confidence

Fusion Builder, a WordPress page builder component, has a privilege escalation vulnerability where users with Contributor-level permissions can gain elevated (Administrator-level) access. The vulnerability exists in versions 3.15.4 and below, likely due to insufficient capability checks or authorization validation in certain builder functions.

MitigationUpdate Fusion Builder to a version newer than 3.15.4. Until the patch is applied, consider restricting or auditing users with Contributor-level permissions, and review user role capabilities on affected sites.

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
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 checks

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

  1. Confirm Fusion Builder is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Fusion Builder' in the list. Note whether it is activated.
    Affected if Fusion Builder plugin is installed and active
  2. Identify the installed Fusion Builder version
    In the Plugins list, find Fusion Builder and note the version number displayed under the plugin name. Alternatively, check the plugin's main PHP file (commonly /wp-content/plugins/fusion-builder/) for a version constant.
    Affected if Version is 3.15.4 or lower
  3. Verify the presence of Contributor-level users
    In WordPress admin, go to Users > All Users and review the 'Role' column. Count or note any users assigned the 'Contributor' role.
    Affected if At least one user with Contributor role exists on the site
  4. Check Contributor access to builder functionality
    Log in as a Contributor user (or review role capabilities) and attempt to access Fusion Builder features such as the builder editor, templates, or element insertion. Verify whether these are accessible without Administrator privileges.
    Affected if Contributor role can access Fusion Builder editing or builder functions

The environment is affected if Fusion Builder version is 3.15.4 or below AND at least one Contributor user exists who can access builder 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.

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

Update Fusion Builder to a version newer than 3.15.4. Until the patch is applied, consider restricting or auditing users with Contributor-level permissions, and review user role capabilities on affected sites.

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-2026-56008 — 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-56008 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