CVE-2023-7320VulnerabilityPublished 29 Oct 2025

CVE-2023-7320: WooCommerce (WordPress plugin) · Information Exposure

Affects WooCommerce (WordPress plugin)Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
automattic WooCommerce	Affected *	Fixed in–

AI-suggested

To mitigate CVE-2023-7320, European organizations using WooCommerce should take the following specific actions: 1) Immediately review and restrict CORS policies on the Store API endpoints to allow only trusted origins, preventing unauthorized cross-origin requests. 2) Monitor web server and API access logs for unusual or unexpected requests originating from unknown domains or IP addresses. 3) Apply any official patches or updates released by Automattic for WooCommerce as soon as they become available. 4) If patches are not yet available, consider temporarily disabling the Store API or implementing web application firewall (WAF) rules to block suspicious API requests. 5) Conduct a thorough audit of exposed data to identify any potential leakage and notify affected users if necessary under GDPR requirements. 6) Educate development and security teams about secure CORS configuration and the risks of exposing sensitive APIs publicly. These measures go beyond generic advice by focusing on API-specific controls and compliance considerations.

Description

CVE-2023-7320 is a medium-severity vulnerability in the WooCommerce plugin for WordPress, affecting all versions up to 7.8.2. It arises from improper Cross-Origin Resource Sharing (CORS) configuration on the Store API's REST endpoints, allowing unauthenticated external actors to access sensitive user information, including personally identifiable information (PII). The vulnerability does not require authentication or user interaction and can be exploited remotely over the network. Although no known exploits are currently reported in the wild, the exposure of sensitive data poses privacy risks and potential regulatory compliance issues, especially under GDPR in Europe. Organizations using WooCommerce should prioritize patching or mitigating this issue to prevent unauthorized data disclosure. Countries with high WooCommerce adoption and strict data protection laws are most at risk. Practical mitigations include restricting CORS policies, monitoring API access logs, and applying updates once available.

Impact

For European organizations, the exposure of sensitive user information through this vulnerability can have significant privacy and regulatory consequences. WooCommerce is a popular e-commerce platform in Europe, and many businesses rely on it to handle customer data, including names, addresses, and payment-related information. Unauthorized access to such data can lead to identity theft, fraud, and reputational damage. Additionally, under the GDPR framework, organizations are required to protect personal data and report breaches promptly. Failure to do so can result in substantial fines and legal liabilities. The vulnerability does not affect system integrity or availability but compromises confidentiality, which is critical for maintaining customer trust and compliance. Given the ease of exploitation and the potential scale of affected WooCommerce installations, European e-commerce businesses are at risk of data leakage if they do not address this issue promptly.

Summary

CVE-2023-7320 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) affecting the WooCommerce plugin for WordPress, specifically versions up to and including 7.8.2. The root cause is improper handling of Cross-Origin Resource Sharing (CORS) headers on the Store API's REST endpoints. This misconfiguration allows any external origin to make requests to these endpoints without authentication, thereby exposing sensitive user data such as personally identifiable information (PII). The vulnerability is exploitable remotely without any user interaction or authentication, increasing its risk profile. The CVSS v3.1 base score is 5.3 (medium severity), reflecting the ease of exploitation (network vector, low attack complexity) but limited impact to confidentiality only, with no impact on integrity or availability. No known exploits have been reported in the wild as of the publication date. The vulnerability affects all WooCommerce versions up to 7.8.2, which is widely used in e-commerce websites globally. The exposure of PII can lead to privacy violations and potential non-compliance with data protection regulations such as GDPR. The vulnerability highlights the importance of proper CORS policy configuration to restrict API access to trusted origins only.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2025, 11:54 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats