← WordPress Vulnerabilities
WordPress security by component

WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels

WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Jan 24, 2025; the highest CVE/CNA score is 6.1.

Plugin slug: woocommerce-pdf-invoices-packing-slips-delivery-notes-and-shipping-labels

CVE-2025-24644: WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels: Cross-site scripting

WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.

PublishedJan 24, 2025
Safe version guidanceSee mitigation notes
Safe version
Jan 24, 2025 CVE-2025-24644
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels: Cross-site scripting
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE5.9
NVD4.8
Mar 22, 2024 CVE-2024-0957
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels: Cross-site scripting
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVDPending
Jan 03, 2024 CVE-2023-7068
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels: A security weakness
WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE4.3
NVD6.5