CVE-2026-54193

Avada (Fusion) Builder <= 3.15.4 - Authenticated (Contributor+) Arbitrary File Deletion

2026-06-16 00:00
daroo

Strategic Overview

Status
Patched in 3.15.5
Affected Plugin
Avada (Fusion) Builder
Affected Version
<= 3.15.4
CVSS
8.1High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-54193
View all Avada (Fusion) Builder vulnerabilities

At a glance

CVE-2026-54193 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting versions <= 3.15.4. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.15.5; sites on affected versions should update now. Disclosed June 2026, reported by daroo.

Vulnerability Overview

The Avada (Fusion) Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in all versions up to, and including, 3.15.4. This makes it possible for authenticated attackers, with Contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on integrity, availability.

CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Reaching this weakness in Avada (Fusion) Builder <= 3.15.4 takes an account at Contributor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.

Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For Avada (Fusion) Builder the fix is 3.15.5: builds <= 3.15.4 are affected, anything from 3.15.5 onward is not.

Remediation

Update to version 3.15.5, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Avada (Fusion) Builder 3.15.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-54193https://www.wordfence.com/threat-intel/vulnerabilities/id/ea5533ab-068a-4a94-bf0a-fc15fcfb383bhttps://nvd.nist.gov/vuln/detail/CVE-2026-54193

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C