CVE-2026-49056: WooCommerce PDF Invoices Plugin Unauthenticated Data Exposure
A vulnerability in WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels allows attackers to access sensitive business and customer data without needing to log in. The flaw affects all versions up to and including 4.9.4. An attacker can retrieve information such as invoice details, customer addresses, and order data by making direct requests to the plugin—no authentication or user interaction required. This poses a significant risk to e-commerce sites relying on this plugin, as customer personal information and financial records could be exposed.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Weaknesses (CWE)
- CWE-497
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-15 / 2026-06-17
NVD description (verbatim)
Unauthenticated Sensitive Data Exposure in WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels <= 4.9.4 versions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-49056 is an unauthenticated sensitive data exposure vulnerability (CWE-497) in the WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels plugin. The vulnerability allows remote attackers to access sensitive data over the network without providing credentials. The plugin fails to enforce proper access controls on endpoints or functions that return or generate PDF documents and related invoice metadata. The attack has low complexity—no special conditions or browser tricks are required—and results in confidentiality breach with no integrity or availability impact. The CVSS 3.1 score of 7.5 (HIGH) reflects network accessibility combined with high confidentiality impact.
Business impact
WooCommerce sites using this plugin face exposure of customer personally identifiable information (PII), order histories, shipping addresses, and potentially payment-related metadata. This can lead to regulatory compliance violations under GDPR, CCPA, and PCI DSS if payment card data is inadvertently exposed; reputational damage from data breach notifications; and increased liability if customer information is used for fraud or identity theft. E-commerce operators depend on customer trust; unauthorized disclosure of order and address data directly undermines that trust and may trigger customer churn and legal action.
Affected systems
The WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels plugin in versions 4.9.4 and earlier is vulnerable. Any WooCommerce store running this plugin at or below version 4.9.4 is at risk. The plugin is commonly deployed on small to mid-sized e-commerce sites. Sites using newer versions of the plugin are not affected, provided they have updated past the vulnerable release.
Exploitability
This vulnerability is highly exploitable. It requires no authentication, no special credentials, and no user interaction. An attacker only needs network access and can craft a direct request to the vulnerable plugin endpoint. No sophisticated techniques are needed; standard HTTP requests suffice. The low attack complexity and public disclosure create an urgent exploitation window. However, the vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, meaning active exploitation in the wild has not been officially confirmed or tracked at the time of publication.
Remediation
Site operators must update the WooCommerce PDF Invoices, Packing Slips, Delivery Notes and Shipping Labels plugin to a version newer than 4.9.4. After patching, audit access logs and backups to determine whether sensitive data may have been accessed. Consider implementing additional access controls and WAF rules to block direct requests to invoice and PDF generation endpoints. Rotate any customer data that was exposed and consider notifying affected customers if a breach is confirmed.
Patch guidance
Check the official WooCommerce plugin repository or the vendor's advisory for the patched version number. Update the plugin to the latest available release that supersedes version 4.9.4. Test the update in a staging environment first to ensure compatibility with your WooCommerce theme and other active plugins. After deployment to production, verify that PDF invoice generation and related functionality continue to work as expected and that the sensitive endpoints are no longer accessible without authentication.
Detection guidance
Monitor web server and WAF logs for unusual or repeated requests to paths containing terms such as 'invoice', 'pdf', 'packing-slip', 'shipping-label', or other PDF generation endpoints associated with the plugin. Look for requests lacking valid session tokens or authentication headers. Configure alerts for HTTP 200 responses on sensitive endpoints when no user session is present. Review any exported or downloaded PDF files in recent backups to identify if unauthorized access occurred. Network-based monitoring should flag anomalous outbound data transfers from the web server that coincide with these requests.
Why prioritize this
This vulnerability merits immediate remediation because it exposes sensitive customer and business data with zero barriers to exploitation. The CVSS score of 7.5 reflects high confidentiality impact. Any WooCommerce site running this plugin and connected to the public internet is vulnerable to opportunistic attack. The plugin is widely used, making this a common target. Delaying patching extends the window in which customer data remains at risk.
Risk score, explained
The CVSS 3.1 score of 7.5 (HIGH) is driven by: network accessibility (AV:N), low attack complexity (AC:L), no privilege requirement (PR:N), no user interaction needed (UI:N), and high confidentiality impact (C:H). The vulnerability does not alter or disrupt the system (I:N, A:N), so integrity and availability scores are zero. The score correctly reflects a serious but not critical exposure—data is compromised but the service remains online and functional. Organizations should treat this as a high-priority issue, not a critical emergency requiring immediate shutdown, but one requiring patches within days.
Frequently asked questions
If our site hasn't been actively promoted or indexed by search engines, are we still at risk?
Yes. Attackers do not rely on search engine indexing. They use automated scanning and enumeration of common plugin paths and endpoints. Even obscure or newly launched WooCommerce sites are vulnerable if the plugin is installed. Network exposure alone is sufficient.
Will simply disabling the plugin mitigate the vulnerability without updating?
Disabling the plugin will prevent access to vulnerable endpoints in most cases, but disabling is not a full remediation strategy. You should update to a patched version or remove the plugin entirely if it is no longer needed. Disabling without removing plugin files may leave code artifacts that could be re-enabled by accident or by an attacker if they gain file access through another vulnerability.
Does this vulnerability allow attackers to modify or delete invoices and orders?
No. The vulnerability is limited to confidentiality (reading and exposing sensitive data). The CVSS vector shows no integrity impact (I:N). Attackers cannot modify orders, invoices, or customer data; they can only view and exfiltrate it. However, the data exposure itself is a serious breach.
Are there any workarounds if we cannot patch immediately?
Temporary mitigations include: blocking or rate-limiting requests to the plugin's endpoints at the web application firewall (WAF) or reverse proxy level; restricting network access to the site if feasible; and moving the site behind additional authentication or IP whitelisting. However, these are temporary measures. Patching is the only reliable fix.
This analysis is provided for informational purposes to help organizations understand and remediate security vulnerabilities. SEC.co does not guarantee the completeness or accuracy of vendor patch information; always verify patch version numbers and compatibility against the official vendor advisory and security bulletins. Testing in a staging environment before production deployment is mandatory. This document does not constitute legal advice, breach notification guidance, or liability assessment. Organizations must independently assess their legal and regulatory obligations regarding data breaches and customer notification. Exploitation status and real-world attack activity may change after publication; consult threat intelligence feeds and vendor advisories for the latest updates. Source: NVD (public-domain), retrieved 2026-07-24. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2026-34891HIGHIDPay WooCommerce Unauthenticated Data Exposure – HIGH Severity
- CVE-2026-52694HIGHUnauthenticated Data Exposure in WooCommerce Signature Add-On ≤ 2.0
- CVE-2026-0466MEDIUMAMD uProf Local Privilege Escalation and Denial of Service
- CVE-2026-24618MEDIUMHash Elements Information Disclosure – Patch Guidance
- CVE-2026-44743LOWSAP Business Objects Information Disclosure Vulnerability
- CVE-2026-49077MEDIUMWP eMember Information Disclosure Vulnerability
- CVE-2016-20062HIGHSQL Injection in Simply Poll 1.4.1 WordPress Plugin - Unauthenticated Data Theft
- CVE-2016-20063HIGHSQL Injection in Single Personal Message 1.0.3 – Credential & Data Theft Risk