CVE-2024-39650
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 · uneditedMissing Authorization vulnerability in WPWeb Elite WooCommerce PDF Vouchers allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WooCommerce PDF Vouchers: from n/a through 4.9.4.
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 confidenceMissing Authorization vulnerability in WPWeb Elite WooCommerce PDF Vouchers plugin allows attackers to access functionality not properly constrained by Access Control Lists (ACLs). With a CVSS of 9.8 (Critical), this likely enables unauthenticated or low-privilege users to execute privileged actions within the voucher management system, potentially exposing sensitive PDF voucher generation and redemption functionality.
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< 4.9.5CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the plugin installation directoryCheck your WordPress wp-content/plugins directory for a folder named 'woocommerce-pdf-vouchers' or similar variant containing 'wpweb' and 'voucher' in the nameAffected if The plugin folder exists on the server
-
Identify the installed plugin versionOpen the main plugin PHP file (usually named plugin-name.php) and locate the 'Version' header in the plugin comment block, or check the version in the WordPress admin Plugins pageAffected if The version number found is less than 4.9.5 (e.g., 4.9.4, 4.9.3, 4.0, etc.)
-
Verify WooCommerce is activeCheck that WooCommerce plugin is installed and active in the WordPress admin, as this PDF Vouchers plugin is a WooCommerce extensionAffected if WooCommerce is active and the vulnerable plugin version is below 4.9.5
-
Confirm the plugin handles sensitive voucher operationsReview the plugin functionality to confirm it handles PDF voucher generation, redemption codes, or gift voucher management for WooCommerce ordersAffected if The plugin manages PDF vouchers or gift codes and the installed version is below 4.9.5
You are affected if the WPWeb Elite WooCommerce PDF Vouchers plugin is installed with any version prior to 4.9.5, as the missing authorization vulnerability allows unauthorized access to privileged voucher management functions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.9.5
Implement proper capability checks and authorization validation on all sensitive functions in the plugin, particularly admin-side and voucher processing endpoints. Update to the patched version (4.9.5 or later) when available, and audit user role permissions in WooCommerce.
WooCommerce PDF Vouchers version 4.9.5
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the WooCommerce PDF Vouchers plugin in the list
- 4. Verify the current version is below 4.9.5
- 5. If an update is available, click 'Update Now' to upgrade to version 4.9.5
- 6. Alternatively, download version 4.9.5 from a trusted source and upload via Plugins > Add New > Upload Plugin
- 7. Confirm the plugin displays version 4.9.5 after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-39650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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