CVE-2026-54193
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 · uneditedContributor Arbitrary File Deletion 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 confidenceFusion Builder plugin for WordPress contains an arbitrary file deletion vulnerability allowing users with contributor-level privileges to delete any file on the server file system. This stems from missing authorization checks in the file deletion functionality, where the contributor role (typically restricted to writing draft content) is incorrectly granted file system manipulation capabilities.
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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Fusion Builder plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate 'Fusion Builder' in the list. Note the installed version number displayed.Affected if Fusion Builder plugin is present and active in WordPress
-
Identify the contributor role capabilitiesNavigate to Users > Roles in WordPress admin, or use a role management plugin to inspect the 'Contributor' role. Review the granted capabilities, specifically looking for any file deletion, file manipulation, or filesystem-related permissions.Affected if Contributor role has any file deletion, unlink, or filesystem write capabilities beyond standard content creation
-
Check for file deletion functionality exposureAttempt to access Fusion Builder file deletion features via its frontend endpoints or by inspecting the plugin code in wp-content/plugins/fusion-builder for functions handling file operations, particularly 'unlink' or 'delete' operations.Affected if The plugin exposes any endpoint or function allowing file deletion without elevated capability checks
-
Verify authorization on file operationsCreate a test Contributor user account if not present, then log in as that user and attempt to access any file deletion features in Fusion Builder. Observe whether the request is rejected or allowed.Affected if A user with Contributor role can successfully delete arbitrary files on the server
Your environment is affected if Fusion Builder plugin is installed AND the Contributor role has file deletion capabilities or can access file deletion functionality without proper authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict file deletion operations to administrator-level users only by implementing proper capability checks (like 'delete_plugins' or 'manage_options') before executing any file operations. Consider upgrading to a patched version if available and audit existing contributor accounts for suspicious activity.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54193 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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