Woocommerce Pdf VouchersWordPress extension · Wpwebelite
CVE-2024-56265
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in wpweb WooCommerce PDF Vouchers woocommerce-pdf-vouchers allows Reflected XSS.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 confidenceReflected XSS vulnerability in WooCommerce PDF Vouchers plugin allows attackers to inject malicious JavaScript through unsanitized user input that gets reflected in generated web pages.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedNavigate to WordPress admin > Plugins and look for 'WooCommerce PDF Vouchers' by Wpwebelite in the installed plugins listAffected if Plugin is installed and active
-
Check installed version numberIn Plugins list, click on the plugin name or look at the version column. Alternatively, check the plugin header in /wp-content/plugins/woocommerce-pdf-vouchers/woocommerce-pdf-vouchers.phpAffected if Version is displayed as lower than 4.9.9
-
Confirm vulnerability is exploitableThe reflected XSS affects any page where the plugin reflects user-supplied input (e.g., voucher codes, recipient fields). If the plugin is active and its shortcodes or templates are in use, the unsanitized input points exist.Affected if Plugin version is below 4.9.9 AND the plugin is active on the site
You are affected if the WooCommerce PDF Vouchers plugin by Wpwebelite is installed with a version lower than 4.9.9 and the plugin is active on your WordPress site.
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
Update WooCommerce PDF Vouchers to version 4.9.9 or later to obtain the patched version. If immediate update is not possible, disable the plugin or implement input sanitization as a temporary measure.
WooCommerce PDF Vouchers version 4.9.9
- Back up your WordPress site and database before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find 'WooCommerce PDF Vouchers' plugin and click 'Update now' to update to version 4.9.9
- Alternatively, download version 4.9.9 from the WordPress plugin repository and upload it manually via Plugins > Add New > Upload Plugin
- After updating, clear any caching plugins and test the voucher generation functionality to ensure the plugin works correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Woocommerce Pdf Vouchers
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56265 — 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-56265 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