CVE-2026-10599

Integrate PhonePe with WooCommerce <= 1.2.1 - Unauthenticated Payment Bypass via Transaction ID Reuse

Published Aug 6, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
The Integrate PhonePe with WooCommerce WordPress plugin through 1.2.1 does not validate that a verified payment transaction belongs to the order being marked as paid, nor does it verify the authenticity of its payment-completion request, allowing unauthenticated attackers to reuse a single valid transaction to mark arbitrary orders as paid and bypass payment.

Analysis

AI-generated

Technical impact

The Integrate PhonePe with WooCommerce plugin for WordPress allows an unauthenticated attacker to send a payment‑completion request that re‑uses a previously valid transaction ID. Because the plugin does not verify that the transaction belongs to the order being marked, the attacker can cause the order status to change to ‘paid’ even though no genuine payment has occurred. This vulnerability arises from a lack of proper authentication and authorization checks (CWE-345, CWE-639).

Affected Systems

WordPress installations that have the Integrate PhonePe with WooCommerce plugin version 1.2.1 or earlier are affected. All such sites that process orders through this plugin are at risk, regardless of additional security controls elsewhere.

Risk and Exploitability

The CVSS score of 7.5 classifies the flaw as high severity. The EPSS score of < 1% indicates a very low exploitation probability at the time of analysis, and the vulnerability is not listed in the CISA KEV catalog. Attackers can exploit the issue remotely by sending unauthenticated HTTP requests that reuse a valid transaction ID; once successful, arbitrary orders can be marked as paid, leading to financial loss and fulfillment errors.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Integrate PhonePe with WooCommerce plugin to a version where proper payment‑transaction validation and request authentication are implemented, once an official patch is released.
  • Implement server‑side checks that confirm the payment transaction ID matches the specific order ID and that the request originates from an authenticated source before updating the order status.
  • Ensure that no front‑end interface can change an order status to ‘paid’; restrict such actions to secure backend processes or administrative authentication.
  • Monitor server logs for repeated transaction ID reuse attempts and audit order status changes for anomalies.

Generated by OpenCVE AI on August 7, 2026 at 18:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions integrate Phonepe With Woocommerce
Vendors & Products Wordpress-extensions
Wordpress-extensions integrate Phonepe With Woocommerce
Type Values Removed Values Added
Weaknesses CWE-285
CWE-287
Type Values Removed Values Added
Weaknesses CWE-345
CWE-639
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-285
CWE-287
Type Values Removed Values Added
Description The Integrate PhonePe with WooCommerce WordPress plugin through 1.2.1 does not validate that a verified payment transaction belongs to the order being marked as paid, nor does it verify the authenticity of its payment-completion request, allowing unauthenticated attackers to reuse a single valid transaction to mark arbitrary orders as paid and bypass payment.
Title Integrate PhonePe with WooCommerce <= 1.2.1 - Unauthenticated Payment Bypass via Transaction ID Reuse
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 7, 2026, 1:46 PM
Reserved
Jun 2, 2026, 8:31 AM
Status
Deferred
Published
Aug 6, 2026, 10:16 PM
Modified
Aug 26, 2026, 4:31 PM