dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32451

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
Missing Authorization vulnerability in ThemeFusion Fusion Builder fusion-builder allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Fusion Builder: from n/a through < 3.15.0.

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

Missing Authorization vulnerability in ThemeFusion Fusion Builder allows attackers to exploit incorrectly configured access control security levels. The vulnerability stems from improper access control checks that fail to properly validate user permissions before allowing access to sensitive functionality. This enables unauthorized users to potentially access or manipulate builder features that should require elevated privileges.

MitigationUpgrade Fusion Builder to version 3.15.0 or later to obtain the patched access control configuration. Review user role capabilities and ensure the principle of least privilege is applied to any custom access configurations.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Verify Fusion Builder is installed
    Locate the Fusion Builder plugin or theme in your WordPress installation. Check the plugin/theme directory for 'fusion-builder' or 'ThemeFusion' components, or view the installed plugins in WordPress admin.
    Affected if Fusion Builder is present in the environment
  2. Determine installed Fusion Builder version
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate Fusion Builder to view its current version number. Alternatively, check the version in the theme/plugin header files if accessible via file system.
    Affected if Version cannot be determined or is visible in the plugin listing
  3. Compare version against patched release
    Compare the installed version number to 3.15.0. Any version lower than 3.15.0 contains the vulnerability.
    Affected if Installed version is earlier than 3.15.0 (e.g., 3.14.x, 3.13.x, etc.)
  4. Inspect Fusion Builder access control settings
    In WordPress admin, go to Fusion Builder settings or Theme Options > User Access. Review the access control security levels configured for builder features, particularly any custom role or capability configurations.
    Affected if Access control settings allow lower-privilege users (subscribers, contributors, or unauthenticated users) to access builder features that should require admin or editor privileges

Environment is affected if Fusion Builder is installed with a version earlier than 3.15.0 and has access control configurations that permit unauthorized users to 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Fusion Builder to version 3.15.0 or later to obtain the patched access control configuration. Review user role capabilities and ensure the principle of least privilege is applied to any custom access configurations.

Recommended fix Moderate confidence

Fusion Builder 3.15.0 or later

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Identify the current version of Fusion Builder installed on your WordPress site
  3. 3. Navigate to the WordPress admin dashboard
  4. 4. Go to Plugins > Installed Plugins
  5. 5. Locate Fusion Builder in the plugin list
  6. 6. Check if an update is available for Fusion Builder
  7. 7. If update available, click 'Update Now' to update to the latest version
  8. 8. If automatic update is not available, download Fusion Builder version 3.15.0 or later from ThemeFusion

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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