{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-123145 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-123145 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-123145 is a medium-severity vulnerability in Unknown WooCommerce Stripe Payment Gateway, published on 9 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-123145 and fix it if it is affected.\n\nWhat it is: CVE-2026-123145 is a medium-severity vulnerability in Unknown WooCommerce Stripe Payment Gateway, published on 9 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-123145 in the wild and no public exploit code.\n\nAffected product: Unknown WooCommerce Stripe Payment Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-123145/ (Markdown: https://insights.sbomify.com/CVE-2026-123145/index.md)","id":"CVE-2026-123145","markdown":"https://insights.sbomify.com/CVE-2026-123145/index.md","name":"CVE-2026-123145","record":{"aliases":["GHSA-6hgw-83cf-5q96"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":4.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WooCommerce Stripe Payment Gateway 10.9.0 - 11.0.1 - Customer Password Stored in Plaintext via Express Checkout","id":"CVE-2026-123145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress IvyForms plugin \u003c= 1.5.1 - Broken Access Control vulnerability","id":"CVE-2026-123148"},"nickname":null,"packages":[],"prev":{"headline":"Code injection in Neon","id":"CVE-2026-123139"},"products":["WooCommerce Stripe Payment Gateway"],"published":"2026-11-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-09","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-123145/"}