{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15211 exists.","fix":"No fix has been published for CVE-2026-15211 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15211 is a medium-severity vulnerability in Unknown Subscriptions for WooCommerce, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15211 and fix it if it is affected.\n\nWhat it is: CVE-2026-15211 is a medium-severity vulnerability in Unknown Subscriptions for WooCommerce, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15211 exists.\n\nAffected product: Unknown Subscriptions for WooCommerce. 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-15211/ (Markdown: https://insights.sbomify.com/CVE-2026-15211/index.md)","id":"CVE-2026-15211","markdown":"https://insights.sbomify.com/CVE-2026-15211/index.md","name":"CVE-2026-15211","record":{"aliases":["GHSA-p384-7c3j-gqm7"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can bypass payment validation in Subscriptions for WooCommerce by supplying a valid PayPal token, marking expensive orders as paid without payment.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"The Subscriptions for WooCommerce WordPress plugin before 2.0.1 does not validate the payment amount or bind the PayPal order token to the order being completed on the WooCommerce order-received flow: it captures a client-supplied token and marks the order paid whenever the capture status is COMPLETED, without comparing the captured amount to the order total. This allows an attacker (unauthenticated where guest checkout is enabled) to substitute an approved, uncaptured PayPal order token and have an expensive order marked paid without paying its price.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Subscriptions for WooCommerce \u003c 2.0.1 - Payment Bypass via Attacker-Supplied PayPal Capture Token","id":"CVE-2026-15211","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN)","id":"CVE-2026-15212"},"packages":[],"prev":{"headline":"Login/Signup with Phone Number, OTP Verification \u003c 1.8.71 - Unauthenticated Account Takeover via OTP Brute Force","id":"CVE-2026-15210"},"products":["Subscriptions for WooCommerce"],"published":"2026-08-07","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["Unknown"]},"summary":"Attackers can bypass payment validation in Subscriptions for WooCommerce by supplying a valid PayPal token, marking expensive orders as paid without payment.","url":"https://insights.sbomify.com/CVE-2026-15211/"}