Woocommerce Pdf VouchersWordPress extension · Wpwebelite
CVE-2024-54383
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 · uneditedIncorrect Privilege Assignment vulnerability in wpweb WooCommerce PDF Vouchers woocommerce-pdf-vouchers allows Privilege Escalation.This issue affects WooCommerce PDF Vouchers: from n/a through < 4.9.9.
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 confidenceThe WooCommerce PDF Vouchers plugin by wpweb versions before 4.9.9 contain an incorrect privilege assignment vulnerability that allows authenticated users to escalate their privileges beyond what they are normally assigned. This privilege escalation likely stems from improper capability checks in the plugin's admin or voucher management functions, enabling lower-privileged users (such as subscribers or customers) to gain administrative access.
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
< 4.9.9CVSS 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.
-
Identify if WooCommerce PDF Vouchers plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for folders containing 'woocommerce-pdf-vouchers' or 'woo-commerce-pdf-vouchers'Affected if The WooCommerce PDF Vouchers plugin by Wpwebelite is present on the WordPress site
-
Determine the installed plugin versionIn WordPress admin > Plugins > Installed Plugins, locate the WooCommerce PDF Vouchers plugin and read the version number displayed beneath the plugin name, or inspect the main plugin PHP file for a 'Version:' headerAffected if The installed version is any version lower than 4.9.9 (e.g., 4.9.8, 4.9.7, 4.8.0, etc.)
-
Verify if lower-privileged user roles existIn WordPress admin > Users > Users List, review the roles assigned to existing users. Look for users with roles of 'Subscriber', 'Customer', or 'Guest'Affected if There are users with Subscriber, Customer, or other non-administrative roles registered on the site
-
Check for unauthorized administrative accountsIn WordPress admin > Users > Users List, examine all accounts with Administrator role. Look for accounts you did not create, unfamiliar email addresses, or accounts created recently without your actionAffected if There are administrative accounts that were not created by known administrators or were created around the time the vulnerability could have been exploited
-
Review user role capability changesInspect WordPress user capability tables in the database (wp_usermeta table with meta_key 'wp_capabilities'), or use a user role editor plugin to check if standard user roles have been modified with elevated capabilitiesAffected if Non-administrative roles have been granted capabilities typically reserved for administrators (such as 'manage_options', 'edit_users', or 'delete_users')
-
Check for unexpected privilege escalation activityReview WordPress audit logs, security plugin logs, or server access logs for API calls or admin-ajax.php requests originating from low-privileged user sessions that performed administrative actionsAffected if Low-privileged user accounts have performed actions reserved for administrators, such as creating new users, modifying settings, or accessing admin areas
You are affected if the WooCommerce PDF Vouchers plugin version is below 4.9.9 AND your site has non-administrative user accounts that could have exploited this privilege escalation flaw.
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.9
Upgrade the WooCommerce PDF Vouchers plugin to version 4.9.9 or later to remediate this vulnerability. Additionally, audit existing user accounts for unauthorized privilege escalation and ensure strong role-based access controls are in place.
4.9.9 or later
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'WooCommerce PDF Vouchers' in the plugin list
- Click 'Update now' if an update is available, or click 'Delete' and reinstall version 4.9.9
- Verify the updated version number after the update completes
- Test the voucher functionality to ensure the plugin works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woocommerce Pdf Vouchers
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54383 — 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-54383 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