CVE-2026-115346

Avada | Website Builder For WordPress & WooCommerce <= 7.16.2 - Unauthenticated Arbitrary File Upload via Avada Form Upload Field

2026-10-30 16:12
Muhamad Visat

Strategic Overview

Status
Patched in 7.16.4
Affected Version
<= 7.16.2
CVSS
8.1High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2026-115346
View all Avada | Website Builder For WordPress & WooCommerce vulnerabilities

At a glance

CVE-2026-115346 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Avada WordPress theme, affecting versions <= 7.16.2. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 7.16.4; sites on affected versions should update now. Disclosed October 2026, reported by Muhamad Visat.

Vulnerability Overview

The Avada | Website Builder For WordPress & WooCommerce theme for WordPress is vulnerable to Arbitrary File Upload in versions up to, and including, 7.16.2 via the convert_palette_images_to_truecolor() function. This is due to insufficient file type validation before processing uploaded files. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Avada <= 7.16.2 carries this weakness at convert_palette_images_to_truecolor(), and reaching it takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For Avada the fix is 7.16.4: builds <= 7.16.2 are affected, anything from 7.16.4 onward is not.

Remediation

Update to version 7.16.4, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Avada 7.16.4 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

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