dbcve.org
Woocommerce Pdf VouchersWordPress extension · Wpwebelite

CVE-2024-39652

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 4.9.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in WPWeb Elite WooCommerce PDF Vouchers allows Reflected XSS.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 · high confidence

Reflected XSS vulnerability in WPWeb Elite WooCommerce PDF Vouchers plugin allows attackers to inject malicious scripts through unsanitized user input that gets reflected in web pages without proper encoding. The vulnerability exists in the plugin's web page generation logic.

MitigationUpdate WooCommerce PDF Vouchers to version 4.9.5 or later. Until patched, avoid clicking untrusted links and implement WAF rules to block XSS attack patterns.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify plugin installation
    Navigate to WordPress admin > Plugins and locate 'WooCommerce PDF Vouchers' by WPWeb Elite in the installed plugins list
    Affected if The plugin is installed and active
  2. Check plugin version
    In the Plugins list, click on the plugin to view its details, or check the plugin header in /wp-content/plugins/woocommmerce-pdf-vouchers/ directory for the version number
    Affected if Version is lower than 4.9.5 (e.g., 4.9.4, 4.9.0, etc.)
  3. Verify plugin is active
    Confirm the plugin status shows 'Active' in the WordPress plugins admin page
    Affected if Plugin is currently active and generating pages with user input
  4. Inspect page generation for unsanitized input
    Use browser developer tools or a proxy to examine HTTP responses from pages generated by the plugin. Look for user-supplied parameters (like query strings) that appear reflected in the HTML output without proper encoding
    Affected if User input from URL parameters is reflected in the page HTML without escaping (e.g., <script> tags or event handlers visible in the response)

You are affected if the WooCommerce PDF Vouchers plugin version is below 4.9.5 and the plugin is active on a page that reflects user input in the response.

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. Until patched, avoid clicking untrusted links and implement WAF rules to block XSS attack patterns.

Recommended fix Moderate confidence

4.9.5

  1. Backup your WordPress site before making any changes
  2. Update WooCommerce PDF Vouchers plugin to version 4.9.5 or later through the WordPress admin dashboard (Plugins > Installed Plugins > Update Now)
  3. Verify the update was successful by checking the plugin version
  4. Clear any caching plugins or server-side caches if applicable
  5. Test the voucher functionality to ensure the update didn't break legitimate functionality

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

Fix this in Woocommerce Pdf Vouchers Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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