CVE-2025-31022: PayU India (WordPress plugin) · Authentication Bypass Using an Alternate Path or Channel
Affects PayU India (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.8.8 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.8.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 9 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade PayU India (WordPress plugin) to 3.8.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PayU PayU India | Affected
| Fixed in
|
AI-suggested
Immediate mitigation steps include: 1) Monitoring for official patches or updates from PayU and applying them promptly once available. 2) Implementing additional layers of authentication and transaction verification, such as multi-factor authentication (MFA) and anomaly detection, to reduce reliance on the vulnerable authentication path. 3) Conducting thorough security assessments of all payment integration points to identify and isolate alternate paths or channels that could be exploited. 4) Employing network-level controls like Web Application Firewalls (WAFs) with custom rules to detect and block suspicious authentication attempts or unusual traffic patterns targeting PayU endpoints. 5) Enhancing logging and monitoring to detect potential exploitation attempts early. 6) Engaging with PayU support to understand the scope of affected versions and timelines for remediation. 7) For organizations with critical dependencies, considering temporary migration to alternative payment gateways until the vulnerability is resolved. These measures go beyond generic advice by focusing on compensating controls and proactive detection tailored to the nature of the authentication bypass.
Description
Authentication Bypass Using an Alternate Path or Channel vulnerability in PayU PayU India allows Authentication Abuse.This issue affects PayU India: from n/a before 3.8.8.