# CVE-2023-7320: WooCommerce <= 7.8.2 - Sensitive Information Exposure

> Unauthenticated attackers can extract sensitive user PII via improper CORS handling on Store API endpoints in WooCommerce.

- **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:** 29 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-26xv-gjx4-vj92

## What is CVE-2023-7320?

CVE-2023-7320 is a medium-severity vulnerability in automattic WooCommerce, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WooCommerce plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 7.8.2, due to improper CORS handling on the Store API's REST endpoints allowing direct external access from any origin. This can allow unauthenticated attackers to extract sensitive user information including PII(Personal Identifiable Information).

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

## Which versions are affected by CVE-2023-7320?


## How do I fix CVE-2023-7320?

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

## Is CVE-2023-7320 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7320 and fix it if it is affected.

What it is: CVE-2023-7320 is a medium-severity vulnerability in automattic WooCommerce, published on 29 Oct 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-2023-7320 in the wild and no public exploit code.

Affected product: automattic 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-2023-7320/ (Markdown: https://insights.sbomify.com/CVE-2023-7320/index.md)
```

## Sources

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

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