# CVE-2026-9612: WhatsOrder <= 1.0.1 - Unauthenticated Sensitive Information Exposure via Predictable Invoice File URLs

> Unauthenticated attackers can access sensitive customer PII and order details by enumerating predictable invoice URLs in the WhatsOrder plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 24 Jun 2026
- **Also known as:** GHSA-xwgw-9h6v-6mv7

## What is CVE-2026-9612?

CVE-2026-9612 is a medium-severity vulnerability in yapacdev WhatsOrder – Instant Checkout for WooCommerce, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WhatsOrder – Instant Checkout for WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.0.1 via the yapacdev_generate_order_pdf. This makes it possible for unauthenticated attackers to extract sensitive customer PII and order details — including full name, email address, phone number, billing address, ordered items with quantities and prices, applied coupons, shipping method, and order total — from any customer's invoice by enumerating sequential order IDs. Invoice HTML files are written to the publicly accessible wp-content/uploads/whatsorder_invoices/ directory, which is created without an .htaccess deny rule or index.php guard, making every invoice directly downloadable over HTTP with no authentication check.

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

## Which versions are affected by CVE-2026-9612?


## How do I fix CVE-2026-9612?

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

## Is CVE-2026-9612 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9612 and fix it if it is affected.

What it is: CVE-2026-9612 is a medium-severity vulnerability in yapacdev WhatsOrder – Instant Checkout for WooCommerce, published on 24 Jun 2026. 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-2026-9612 in the wild and no public exploit code.

Affected product: yapacdev WhatsOrder – Instant Checkout for WooCommerce. 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-2026-9612/ (Markdown: https://insights.sbomify.com/CVE-2026-9612/index.md)
```

## Sources

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

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