dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-14352

HIGH · 7.5 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 AR for WooCommerce plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 8.40 via the 'file' parameter parameter. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information. The three intended access controls all fail: valid nonces are freely minted by unauthenticated callers via the nopriv ar_get_fresh_nonce and ar_process_user_image AJAX handlers; the AES-256-CBC encryption key is derived from get_option('ar_licence_key'), which returns false on default free installations and yields a predictable key attackers can use to encrypt their own path payloads; and the Referer check is trivially bypassed because the Referer header is attacker-controlled.

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 AR for WooCommerce plugin for WordPress versions up to 8.40 contains a directory traversal vulnerability in the 'file' parameter, allowing unauthenticated attackers to read arbitrary files on the server. Three security controls fail simultaneously: nonce validation is bypassed via AJAX handlers that mint valid nonces for unauthenticated users, the AES-256-CBC encryption key is derived from a license key option that returns false on free installations yielding a predictable key, and the Referer check is trivially bypassed since attackers control the header.

MitigationUpgrade to a version beyond 8.40 which contains proper path validation, secure nonce generation, and encryption key handling; until then, consider disabling the plugin or implementing web application firewall rules to block directory traversal patterns in request parameters.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 AR for WooCommerce plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'AR for WooCommerce' or check the plugins directory via file system for /wp-content/plugins/ar-woocommerce/
    Affected if Plugin is present and active
  2. Check installed version against affected range
    Inspect the plugin's main PHP file header or version.php for the version number; compare to the affected range (any version up to and including 8.40)
    Affected if Version is 8.40 or lower
  3. Identify vulnerable AJAX endpoint with file parameter
    Search plugin files for AJAX handlers that process a 'file' parameter, typically in ajax.php or similar endpoint files; look for functions handling file downloads or includes that accept user input
    Affected if The plugin exposes an AJAX endpoint accepting a 'file' parameter for directory traversal
  4. Confirm free tier installation (predictable encryption key)
    Check the WordPress options table or plugin settings for the license key option; on free installations this typically returns false or an empty value, yielding a predictable AES-256-CBC key
    Affected if Plugin is a free version without a valid license key configured

If the AR for WooCommerce plugin is installed at version 8.40 or lower and exposes an AJAX endpoint handling a 'file' parameter, the environment is likely vulnerable to unauthenticated directory traversal.

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

Upgrade to a version beyond 8.40 which contains proper path validation, secure nonce generation, and encryption key handling; until then, consider disabling the plugin or implementing web application firewall rules to block directory traversal patterns in request parameters.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14352 — 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-14352 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