CVE-2026-3464

WP Customer Area <= 8.3.4 - Authenticated (Subscriber+) Arbitrary File Read/Deletion via ajax_attach_file

2026-04-17 04:24
shark3y

Strategic Overview

Status
Patched in 8.3.5
Affected Plugin
WP Customer Area
Affected Version
<= 8.3.4
CVSS
8.8High
Weakness type
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE
CVE-2026-3464
View all WP Customer Area vulnerabilities

At a glance

CVE-2026-3464 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the WP Customer Area WordPress plugin, affecting versions <= 8.3.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 8.3.5; sites on affected versions should update now. Disclosed April 2026, reported by shark3y.

Vulnerability Overview

The WP Customer Area plugin for WordPress is vulnerable to arbitrary file read and deletion due to insufficient file path validation in the 'ajax_attach_file' function in all versions up to, and including, 8.3.4. This makes it possible for authenticated attackers with a role that an administrator grants access to (e.g., Subscriber) to to read the contents of arbitrary files on the server, which can contain sensitive information, or 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 confidentiality, integrity, availability — full site compromise territory.

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

WP Customer Area <= 8.3.4 carries this weakness at ajax_attach_file, and reaching it takes an account at Subscriber 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 WP Customer Area the fix is 8.3.5: builds <= 8.3.4 are affected, anything from 8.3.5 onward is not.

Remediation

Update to version 8.3.5, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber 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: WP Customer Area 8.3.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-3464https://www.wordfence.com/threat-intel/vulnerabilities/id/aadf1f4c-c852-4167-9b09-7e679a953725https://nvd.nist.gov/vuln/detail/CVE-2026-3464

Related records

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