dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-3464

HIGH · 8.8 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Customer Area WordPress plugin versions up to 8.3.4 contain a path traversal vulnerability in the ajax_attach_file function that allows authenticated users with minimal privileges (e.g., Subscriber role) to read or delete arbitrary files on the server due to insufficient file path validation and sanitization.

MitigationUpdate the plugin to version 8.3.5 or later which patches the path validation vulnerability. Until patched, remove the plugin or restrict file attachment capabilities to trusted administrator-level users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Customer Area plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'WP Customer Area' or 'WP Customer Area - File Protection' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is active.
  2. Check the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the WP Customer Area plugin to view its details, or check the version in the plugin's main PHP file header (typically wp-content/plugins/wp-customer-area/includes/class-wpcu-core.php or similar main file).
    Affected if The displayed version is 8.3.4 or any version below 8.3.5.
  3. Confirm minimal-privilege user roles exist
    Navigate to Users > All Users in the WordPress admin panel. Review the list to identify if any users have the 'Subscriber' role assigned, or check under Users > User Roles to see if Subscriber role is defined.
    Affected if There are users assigned the Subscriber role or any role below Administrator.
  4. Check if file attachment functionality is enabled
    Navigate to Customer Area > Settings or similar configuration page in the WordPress admin. Look for settings related to 'File Attachments', 'ajax_attach_file', 'Upload Files', or 'Protected Files'.
    Affected if File attachment or upload features are enabled or accessible to non-administrator users.
  5. Inspect the ajax_attach_file function accessibility
    If you have access to the plugin source code, locate the ajax_attach_file function in the plugin files (typically in ajax-handlers.php or similar). Verify if the function is hooked to a WordPress AJAX action (wp_ajax_ or wp_ajax_nopriv_) and check if it lacks capability checks or role restrictions.
    Affected if The ajax_attach_file function is hooked to an AJAX action without proper capability checks allowing subscriber-level access.

You are affected if WP Customer Area plugin version 8.3.4 or lower is installed, file attachment features are enabled, and user accounts with Subscriber-level or higher privileges exist in your WordPress environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 8.3.5 or later which patches the path validation vulnerability. Until patched, remove the plugin or restrict file attachment capabilities to trusted administrator-level users only.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation5.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,260
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3464 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3464 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data