# CVE-2025-24373: Unrestricted Access to PDF Documents via URL Manipulation in woocommerce-pdf-invoices-packing-slips

> Unauthorized users can access sensitive PDF documents by manipulating URLs when guest access is enabled, requiring an upgrade to fix.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-3j9m-cp35-94fr

## What is CVE-2025-24373?

CVE-2025-24373 is a medium-severity missing authorization vulnerability in wpovernight woocommerce-pdf-invoices-packing-slips, published on 4 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

woocommerce-pdf-invoices-packing-slips is an extension which allows users to create, print & automatically email PDF invoices & packing slips for WooCommerce orders. This vulnerability allows unauthorized users to access any PDF document from a store if they: 1. Have access to a guest document link and 2. Replace the URL variable `my-account` with `bulk`. The issue occurs when: 1. The store's document access is set to "guest." and 2. The user is logged out. This vulnerability compromises the confidentiality of sensitive documents, affecting all stores using the plugin with the guest access option enabled. This issue has been addressed in version 4.0.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-24373?

It affects 1 product.


Products: Wpovernight Woocommerce Pdf Invoices\& Packing Slips.

## How do I fix CVE-2025-24373?

No fix has been published for CVE-2025-24373 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-24373 being exploited?

There is no known exploitation of CVE-2025-24373 in the wild and no public exploit code.

## Other vulnerabilities in wpovernight woocommerce-pdf-invoices-packing-slips

- [CVE-2024-22147](https://insights.sbomify.com/CVE-2024-22147/): WordPress WooCommerce PDF Invoices & Packing Slips Plugin <= 3.7.5 is vulnerable to SQL Injection (high 7.6)
- [CVE-2024-3045](https://insights.sbomify.com/CVE-2024-3045/): PDF Invoices & Packing Slips for WooCommerce <= 3.8.0 - Unauthenticated Stored Cross-Site Scripting (high 7.2)
- [CVE-2024-3047](https://insights.sbomify.com/CVE-2024-3047/): PDF Invoices & Packing Slips for WooCommerce <= 3.8.0 - Unauthenticated Server-Side Request Forgery (high 7.2)
- [CVE-2022-2537](https://insights.sbomify.com/CVE-2022-2537/): WooCommerce PDF Invoices & Packing Slips < 3.0.1 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2022-2092](https://insights.sbomify.com/CVE-2022-2092/): WooCommerce PDF Invoices & Packing Slips < 2.16.0 - Reflected Cross-Site Scripting (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24373 and fix it if it is affected.

What it is: CVE-2025-24373 is a medium-severity missing authorization vulnerability in wpovernight woocommerce-pdf-invoices-packing-slips, published on 4 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24373 in the wild and no public exploit code.

Affected product: wpovernight woocommerce-pdf-invoices-packing-slips. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24373/ (Markdown: https://insights.sbomify.com/CVE-2025-24373/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24373
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24373
- OSV: https://osv.dev/vulnerability/CVE-2025-24373

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24373/
Summaries are generated and may contain mistakes; the official description above is the record.