Quick answers
- Is CVE-2026-123145 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123145 being exploited in the wild.
- How severe is CVE-2026-123145?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- WooCommerce Stripe Payment Gateway 10.9.0 through 11.0.1.
- Is there a fix for CVE-2026-123145?
- Yes: fixed in 11.1.0. Until then: Upgrade to version 11.1.0, which removes stored plaintext passwords on update. Until then, restrict database access and review order metadata for exposed credentials. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123145 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-123145?
- Check whether you run WooCommerce Stripe Payment Gateway at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 11.1.0
Upgrade to version 11.1.0, which removes stored plaintext passwords on update. Until then, restrict database access and review order metadata for exposed credentials.
Technical details
The plugin fails to exclude the account password from checkout fields saved to order metadata during express checkout, storing plaintext passwords in the database (versions 10.9.0–11.0.1). Version 10.9.1 stopped storing new passwords but did not remove previously stored ones; version 11.1.0 removes existing stored passwords on update. An attacker with database or order data access can retrieve these plaintext credentials.
Affected products
- WooCommerce Stripe Payment Gateway 10.9.0 through 11.0.1
Timeline
- 2026-11-06: disclosed
- 2026-11-09: advisory
- 2026-11-09: patched: version 11.1.0 removes stored passwords