dbcve.org
Woocommerce Pdf VouchersWordPress extension · Wpwebelite

CVE-2024-39651

CRITICAL · 9.3 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 4.9.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in WPWeb WooCommerce PDF Vouchers allows File Manipulation.This issue affects WooCommerce PDF Vouchers: from n/a before 4.9.5.

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 · moderate confidence

A path traversal vulnerability in the WooCommerce PDF Vouchers plugin (versions before 4.9.5) allows attackers to manipulate file paths using directory traversal sequences (e.g., ../../../) to access files outside the intended restricted directory. This enables unauthorized file read/write operations on the server, leading to potential remote code execution or data exfiltration.

MitigationUpdate WooCommerce PDF Vouchers to version 4.9.5 or later immediately. If immediate updating is not feasible, disable the plugin and review server access logs for indicators of compromise.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Woocommerce Pdf VouchersWordPress extension
Affected:< 4.9.5

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
Changed
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/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 the WooCommerce PDF Vouchers plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'woocommerce-pdf-vouchers' or similar variation containing 'pdf-vouchers' from the vendor 'wpwebelite'.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Determine the installed plugin version
    Open the main plugin PHP file (usually in the plugin root folder) and locate the version comment in the plugin header, or check the 'Version:' field in the plugin's main file or readme.txt.
    Affected if The reported version number is lower than 4.9.5.
  3. Confirm the vulnerable file handling feature is active
    Review the plugin settings in the WordPress admin panel under the WooCommerce PDF Vouchers menu. Check if voucher template upload, voucher PDF generation, or file download features are enabled.
    Affected if Any file upload, download, or voucher template functionality is enabled in the plugin settings.
  4. Inspect server access logs for path traversal attempts
    Search web server access logs (Apache, Nginx, or equivalent) for requests to the plugin's endpoint containing patterns like '../', '..%2F', URL-encoded traversal sequences, or requests referencing files outside the vouchers upload directory.
    Affected if Log entries contain directory traversal sequences in requests to WooCommerce PDF Vouchers endpoints.

The environment is affected if the WooCommerce PDF Vouchers plugin version is below 4.9.5 and the plugin (or its file handling features) is installed and active.

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.

dbcve · scoped
Upgrade available Upgrade to 4.9.5 or later
Fixed in 4.9.5
Interim mitigation

Update WooCommerce PDF Vouchers to version 4.9.5 or later immediately. If immediate updating is not feasible, disable the plugin and review server access logs for indicators of compromise.

Recommended fix Moderate confidence

WooCommerce PDF Vouchers version 4.9.5

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Navigate to WordPress Admin Dashboard > Plugins
  3. 3. Locate 'WooCommerce PDF Vouchers' in the installed plugins list
  4. 4. Deactivate the current version of the plugin
  5. 5. Delete the current plugin (this is safe as long as you have a backup and will reinstall the new version)
  6. 6. Go to Add New > Upload Plugin and upload version 4.9.5 of WooCommerce PDF Vouchers, or search for it in the WordPress plugin repository and install
  7. 7. Activate the newly installed version 4.9.5
  8. 8. Test PDF voucher generation and download functionality to confirm the plugin works correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Woocommerce Pdf Vouchers Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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