CVE-2026-42661

WP Customer Area <= 8.3.4 - Authenticated (Custom+) Path Traversal

2026-05-01 00:00
iamlooper

Strategic Overview

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

At a glance

CVE-2026-42661 is a medium-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 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.3.5; sites on affected versions should update now. Disclosed May 2026, reported by iamlooper.

Vulnerability Overview

The WP Customer Area plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 8.3.4. This makes it possible for authenticated attackers, with Custom-level access and above, to perform actions on files outside of the originally intended directory.

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 privileges on the target site, and no interaction from a victim user.

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

Reaching this weakness in WP Customer Area <= 8.3.4 takes an account at Custom 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 Custom 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-42661https://www.wordfence.com/threat-intel/vulnerabilities/id/d731f7bf-d2de-4f5f-8c4a-627713bec348https://nvd.nist.gov/vuln/detail/CVE-2026-42661

Related records

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