EUVD-2026-54302
GHSA-x972-w82m-gqc5
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Callback endpoint is network-reachable with no auth; integrity-only impact as attackers fraudulently settle orders but cannot read data or disrupt availability.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Payment bypass in the 'Integrate PhonePe with WooCommerce' WordPress plugin (through version 1.2.1) allows unauthenticated remote attackers to mark arbitrary WooCommerce orders as paid without making actual payment. The plugin fails on two independent validation layers: it does not bind a verified PhonePe transaction ID to the specific order being settled, and it does not authenticate the origin of payment-completion requests. An attacker with one valid transaction ID - obtained from any legitimate purchase, even a minimal-value one - can replay it against any other order on the same store. No public exploit identified at time of analysis, and the vulnerability is not in the CISA KEV catalog.
Technical ContextAI
The affected plugin acts as a WooCommerce payment gateway integration for PhonePe, a widely-used Indian UPI/digital payments processor. In a correctly implemented payment callback flow, the plugin must (1) verify the HMAC or digital signature of the callback to confirm it originated from PhonePe, and (2) assert that the transaction ID in the callback matches the order it is being applied to. Both checks are absent here. The root cause is functionally equivalent to CWE-345 (Insufficient Verification of Data Authenticity) and CWE-639 (Authorization Bypass Through User-Controlled Key) - the order identifier is attacker-supplied and the transaction ID is not order-scoped. The vulnerability exists in the payment-completion handler exposed to handle PhonePe callbacks, which is necessarily unauthenticated to receive incoming webhook-style confirmations from the payment processor.
RemediationAI
No vendor-released patched version is confirmed in the available data - the WPScan advisory at https://wpscan.com/vulnerability/a1aae05d-63d0-4cde-8a9c-996f58f58e48/ should be monitored for an updated release. Until a patch is available, the most effective compensating control is to deactivate the plugin entirely and switch to an alternative PhonePe or WooCommerce payment gateway that performs proper transaction-to-order binding and callback signature verification. If disabling is not operationally feasible, restrict access to the payment-completion callback endpoint at the web server or WAF layer so that only PhonePe's known IP ranges can reach it - note that IP allowlisting is a partial mitigation and does not substitute for cryptographic callback verification. Merchants should also audit recent orders marked as paid via PhonePe for signs of transaction ID reuse across multiple orders.
The mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today