# CVE-2026-94275: Track Orders for WooCommerce < 1.2.7 - Unauthenticated PII Disclosure via 'email' Parameter

> Unauthenticated attackers can retrieve customer PII and order history by supplying an email address due to missing ownership verification.

- **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:** 8 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-f82x-57h2-9789

## What is CVE-2026-94275?

CVE-2026-94275 is a medium-severity vulnerability in Unknown Track Orders for WooCommerce, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Track Orders for WooCommerce  WordPress plugin before 1.2.7 does not verify ownership of an order before returning its billing details, allowing unauthenticated attackers to obtain a customer's name, email address, phone number, postal address and order history by supplying that customer's email address.

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

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


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

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

## Is CVE-2026-94275 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94275 is a medium-severity vulnerability in Unknown Track Orders for WooCommerce, published on 8 Oct 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-94275 in the wild and no public exploit code.

Affected product: Unknown Track Orders 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-94275/ (Markdown: https://insights.sbomify.com/CVE-2026-94275/index.md)
```

## Sources

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

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