CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 4.1.1.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.18% · 8th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Read the original 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.
Who should check
Teams running WooCommerce stores with the wp.insider Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions plugin before 4.1.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 4.1.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- wp.insider Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce
fixed in 4.1.1
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-127204
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: cve.now feed data
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: vulncheck.com
Which versions are affected by CVE-2026-127204?
Payment Gateway for PayPal Pro, PayPal Checkout & Subscriptions for WooCommerce: before 4.1.1.Source: cve.now feed data
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: vulncheck.com
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: vulncheck.com