Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-8713 – Unauthenticated Arbitrary File Deletion Leading to RCE – Avada (Fusion) Builder W…

Be the first to know when new zero-days emerge:

Summary

CVE-2026-8713 is a critical unauthenticated arbitrary file deletion vulnerability in the Avada (Fusion) Builder WordPress plugin, affecting all versions up to and including 3.15.3. The flaw stems from insufficient file path validation in the maybe_delete_files() function, allowing unauthenticated remote attackers to delete arbitrary files on the server — including wp-config.php — which can directly result in full site takeover and remote code execution. With over one million active installations, the potential attack surface is exceptionally wide, and a patch was released on June 2, 2026 in version 3.15.4.

Technical details

  • Root cause: The maybe_delete_files() function within the Fusion_Form_DB_Entries class performs no realpath resolution or upload-directory containment check, allowing path traversal sequences to escape the intended upload directory and reach arbitrary files on the server.
  • Attack vector: An unauthenticated attacker submits a form payload containing a path traversal string (e.g., referencing wp-config.php via ../../ sequences) through the wp_ajax_nopriv_fusion_form_submit_ajax AJAX handler, which requires no credentials.
  • Trigger conditions: Exploitation requires that a published Avada form be configured to save entries to the database — a standard and common deployment configuration. The attacker additionally controls the fusion_privacy_expiration_interval and privacy_expiration_action fields to force an immediate "delete" cleanup action, causing the submitted malicious path to be processed by the Fusion_Form_DB_Privacy shutdown hook without any administrator interaction.
  • Impact: Deletion of critical server files. Removing wp-config.php renders the site unconfigured, enabling an attacker to reconnect it to a malicious database and install arbitrary code, effectively achieving remote code execution. Other critical files may also be targeted.

Affected software

  • Avada (Fusion) Builder WordPress Plugin — all versions up to and including 3.15.3

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
  • CWE: CWE-22 – Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

Mitigation and recommended actions

  • Immediate action: Update the Avada (Fusion) Builder plugin to version 3.15.4 or later (released June 2, 2026 as part of Avada 7.15.4). This release addresses the file path validation flaw in maybe_delete_files().
  • If immediate patching is not feasible, consider temporarily disabling Avada forms that are configured to save entries to the database until the update can be applied.
  • Audit web server file integrity monitoring for unexpected deletions of wp-config.php or other core WordPress files, which may indicate prior exploitation.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge