# CVE-2026-103376: PeachPay 1.117.9 - 1.120.69 - Unauthenticated Order Key Disclosure via ConvesioPay BTCPay Status Check

> Unauthenticated attackers can retrieve secret order keys to view sensitive customer data in the PeachPay WooCommerce plugin.

- **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:** 17 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** GHSA-pvfc-2cxg-992w

## What is CVE-2026-103376?

CVE-2026-103376 is a medium-severity missing authorization vulnerability in Unknown PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI), published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI) WordPress plugin before 1.120.70 does not perform any capability or ownership check before returning an order's secret key in response to an unauthenticated request, allowing anyone to retrieve the key for any paid order and use it to view that order's customer name, email address, postal address and contents.

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

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


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

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

## Is CVE-2026-103376 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103376 is a medium-severity missing authorization vulnerability in Unknown PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI), published on 17 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-103376 in the wild and no public exploit code.

Affected product: Unknown PeachPay — Payments & Express Checkout for WooCommerce (supports Stripe, PayPal, Square, Authorize.net, NMI). 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-103376/ (Markdown: https://insights.sbomify.com/CVE-2026-103376/index.md)
```

## Sources

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

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