# CVE-2026-123145: WooCommerce Stripe Payment Gateway 10.9.0 - 11.0.1 - Customer Password Stored in Plaintext via Express Checkout


- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-6hgw-83cf-5q96

## What is CVE-2026-123145?

CVE-2026-123145 is a medium-severity vulnerability in Unknown WooCommerce Stripe Payment Gateway, published on 9 Nov 2026. 

### Official description

The WooCommerce Stripe Payment Gateway WordPress plugin before 11.1.0 does not exclude the account password from the checkout fields it saves to order metadata during express checkout, causing the password a customer chooses when creating an account at checkout to be stored in plaintext in the database, readable by anyone with access to order data or the database. Version 10.9.0 stored the passwords. Version 10.9.1 stopped new ones from being stored but left existing ones in place, and version 11.1.0 removes them on update. Passwords stored this way should be considered exposed.

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

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


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

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

## Is CVE-2026-123145 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123145 is a medium-severity vulnerability in Unknown WooCommerce Stripe Payment Gateway, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123145 in the wild and no public exploit code.

Affected product: Unknown WooCommerce Stripe Payment Gateway. 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-123145/ (Markdown: https://insights.sbomify.com/CVE-2026-123145/index.md)
```

## Sources

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

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