themefusion Avada Builder Plugin up to 3.15.3 on WordPress Path Validation wp-config.php maybe_delete_files privacy_expiration_action path traversal

Summaryinfo

A vulnerability was found in themefusion Avada Builder Plugin up to 3.15.3 on WordPress. It has been rated as critical. The affected element is the function maybe_delete_files of the file wp-config.php of the component Path Validation Handler. The manipulation of the argument privacy_expiration_action leads to path traversal. This vulnerability is listed as CVE-2026-8713. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as critical, has been found in themefusion Avada Builder Plugin up to 3.15.3 on WordPress. This issue affects the function maybe_delete_files of the file wp-config.php of the component Path Validation Handler. The manipulation of the argument privacy_expiration_action with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is integrity, and availability. The summary by CVE is:

The Avada (Fusion) Builder plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the maybe_delete_files function in all versions up to, and including, 3.15.3. This makes it possible for unauthenticated attackers 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). The attack requires a published Avada form configured to save entries to the database; an unauthenticated attacker submits a path-traversal payload via the wp_ajax_nopriv_fusion_form_submit_ajax handler while also controlling the fusion_privacy_expiration_interval and privacy_expiration_action fields to force an immediate 'delete' cleanup, causing the planted entry to be automatically processed by the Fusion_Form_DB_Privacy shutdown-hook routine without any administrator interaction.

The weakness was presented by daroo. It is possible to read the advisory at wordfence.com. The identification of this vulnerability is CVE-2026-8713 since 05/15/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/19/2026). The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

By approaching the search of inurl:wp-config.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• themefusion

Name

• Avada Builder Plugin

Version

• 3.15.0
• 3.15.1
• 3.15.2
• 3.15.3

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion