dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-54194

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
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
Contributor PHP Object Injection 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

A PHP Object Injection vulnerability in Fusion Builder (a WordPress page builder plugin) affecting versions up to 3.15.4 allows authenticated users with contributor-level permissions to inject malicious PHP objects through unsafe deserialization of untrusted data, potentially leading to remote code execution.

MitigationUpgrade Fusion Builder to a version newer than 3.15.4. If an updated version is not yet available, limit or temporarily revoke contributor-level user permissions and audit user accounts for suspicious activity.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify Fusion Builder plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > locate Fusion Builder (or Avada Fusion Builder) and check the version number displayed
    Affected if The installed version is 3.15.4 or any earlier version up to and including 3.15.4
  2. Confirm Fusion Builder is active
    Check the Plugins list in WordPress admin; ensure the plugin status shows as 'Active'
    Affected if Fusion Builder is installed and active with a vulnerable version (3.15.4 or earlier)
  3. Identify contributor-level user accounts
    Go to WordPress admin > Users > All Users; look for any accounts with the 'Contributor' role
    Affected if There are one or more user accounts assigned the Contributor role
  4. Audit recent contributor user activity
    Review WordPress activity logs, server access logs, or user session data for any unusual posts, pages, or serialized data submissions from contributor accounts
    Affected if There is evidence of serialized data being submitted or unexpected code patterns in contributor-submitted content

You are affected if Fusion Builder version 3.15.4 or earlier is installed and active, and at least one contributor-level user account exists 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

Upgrade Fusion Builder to a version newer than 3.15.4. If an updated version is not yet available, limit or temporarily revoke contributor-level user permissions and audit user accounts for suspicious activity.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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