Unauthenticated PII disclosure via permissive Store API CORS
Published Oct 29, 2025 · Updated Oct 29, 2025
Information exposure in Automattic WooCommerce 7.8.2 and earlier allows remote attackers to read customer PII through Store API requests. Affected Store API code leaves WordPress's default REST CORS handler enabled, which reflects arbitrary Origin values while permitting credentials on PII-bearing responses. No WooCommerce account or API key is required; exposure is limited to affected API responses, with no reported write or availability impact.
Summary
What happened
Information exposure in Automattic WooCommerce 7.8.2 and earlier allows remote attackers to read customer PII through Store API requests. Affected Store API code leaves WordPress's default REST CORS handler enabled, which reflects arbitrary Origin values while permitting credentials on PII-bearing responses. No WooCommerce account or API key is required; exposure is limited to affected API responses, with no reported write or availability impact.
The record
- CVE
- CVE-2023-7320
- Published
- Oct 29, 2025
- Updated
- Oct 29, 2025
- Vendor
- WooCommerce
- Product
- WooCommerce
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 29, 2025CVE publishedPublication date reported by the CVE source.
- Oct 29, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=* <=7.8.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo