# CVE-2025-14073: WooCommerce PayPal Payments <= 3.3.2 - Unauthenticated Sensitive Information Disclosure

> Unauthenticated attackers can obtain sensitive order keys to access customer billing details via the Store API shortly after order creation.

- **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:** 1 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-p553-vwc7-337r

## What is CVE-2025-14073?

CVE-2025-14073 is a medium-severity vulnerability in WooCommerce PayPal Payments, published on 1 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WooCommerce PayPal Payments plugin for WordPress is vulnerable to Sensitive Information Disclosure due to an Insecure Direct Object Reference in all versions up to, and including, 3.3.2 via the `enqueue_paypal_insights_script_on_order_received()` function due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to obtain sensitive order information including order keys, which can then be leveraged to access full customer billing details (name, email, phone, address) via the WooCommerce Store API within a 10-minute grace period after order creation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2025-14073?


## How do I fix CVE-2025-14073?

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

## Is CVE-2025-14073 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14073 and fix it if it is affected.

What it is: CVE-2025-14073 is a medium-severity vulnerability in WooCommerce PayPal Payments, published on 1 Aug 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-2025-14073 in the wild and no public exploit code.

Affected product: WooCommerce PayPal Payments. 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-2025-14073/ (Markdown: https://insights.sbomify.com/CVE-2025-14073/index.md)
```

## Sources

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

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