PatchSiren cyber security CVE debrief
CVE-2026-92400 WooCommerce CVE debrief
The Payment Gateway for PayPal on WooCommerce WordPress plugin before 9.2.1 does not verify that an incoming payment notification was confirmed in the store's configured payment environment or paid to the store's own merchant account before marking an order complete, allowing unauthenticated users to mark their own orders as paid using a genuine transaction from a payment sandbox they control.
- Vendor
- WooCommerce
- Product
- Payment Gateway for PayPal on WooCommerce
- CVSS
- MEDIUM 5.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-21
- Original CVE updated
- 2026-09-21
- Advisory published
- 2026-09-21
- Advisory updated
- 2026-09-21
Who should care
Defenders responsible for WordPress installations using the Payment Gateway for PayPal on WooCommerce plugin should assess exposure and prioritize verification of the payment gateway configuration.
Why it matters
CVE-2026-92400 allows unauthenticated users to mark orders as paid, potentially leading to financial losses or incorrect order fulfillment.
- Defenders must verify payment gateway configurations to prevent unauthorized order modifications.
- Monitoring order status updates is crucial to detect potential exploitation attempts.
- The vulnerability may require additional logging and auditing to detect and respond to potential exploitation.
Technical summary
The vulnerability allows unauthenticated users to mark their own orders as paid using a genuine transaction from a payment sandbox they control, due to a lack of verification of incoming payment notifications. This issue affects the Payment Gateway for PayPal on WooCommerce WordPress plugin before version 9.2.1. Defenders should prioritize verifying the payment gateway configuration and monitoring order status updates to prevent unauthorized modifications. The vulnerability could lead to financial losses or incorrect order fulfillment if exploited.
Defensive priority
Defenders should prioritize verifying the payment gateway configuration and monitoring order status updates to prevent unauthorized modifications.
Recommended defensive actions
- Verify the payment gateway configuration to prevent unauthorized modifications.
- Monitor order status updates to detect potential exploitation attempts.
- Update the plugin to version 9.2.1 or later if possible.
- Review compensating controls for exposed systems while remediation is scheduled and verified.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
- Track exceptions, retest remediated assets, and close the item only after evidence is documented.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but additional verification is required to determine the full scope of affected systems and potential impact. Defenders should verify the payment gateway configuration and monitor order status updates to prevent unauthorized modifications. The vulnerability allows unauthenticated users to mark their own orders as paid using a genuine transaction from a payment sandbox they control. Evidence from the CVE Program and NVD suggests that the Payment Gateway for PayPal on 9.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-92400 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-92400
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-92400 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-92400
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://wpscan.com/vulnerability/3dcee743-a95d-4233-b78e-8449a6cc8aea/
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.