dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-22334

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
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

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
Subscriber Arbitrary File Download in Woocommerce Book Price <= 1.3 versions.

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 Woocommerce Book Price plugin <= 1.3 versions contains an arbitrary file download vulnerability that allows authenticated users with subscriber-level privileges to download arbitrary files from the server file system via improper validation of user-supplied file path parameters.

MitigationUpgrade the Woocommerce Book Price plugin to version 1.4 or later, which contains the security fix for this vulnerability.

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 plugin installation and version
    Navigate to WordPress admin > Plugins and locate 'Woocommerce Book Price' in the installed plugins list. Check the version number displayed under the plugin name. Compare this version against the affected range (<= 1.3).
    Affected if The installed version is 1.3 or lower.
  2. Confirm plugin is active
    In the same Plugins page, verify that the Woocommerce Book Price plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.
    Affected if The plugin is active and the version is 1.3 or lower.
  3. Identify subscriber-level users
    Go to WordPress admin > Users and review the user list. Check the 'Role' column for any users assigned the 'Subscriber' role. Note the count and usernames of these users.
    Affected if There exists at least one user with Subscriber role (or any role ranked below Administrator/Editor/Author) who could potentially access the vulnerable functionality.
  4. Locate file download functionality
    Inspect the plugin files (typically in wp-content/plugins/woocommerce-book-price/) for code handling file download requests, looking for functions that accept user-supplied file path parameters (such as file, path, download_file, or similar query parameters in GET/POST requests).
    Affected if The plugin contains file download functionality that accepts user-controlled path parameters without proper validation.

You are affected if the Woocommerce Book Price plugin version 1.3 or lower is installed and active, and your site has subscriber-level users who could access the vulnerable file download feature.

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 the Woocommerce Book Price plugin to version 1.4 or later, which contains the security fix for this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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