Unauthenticated account takeover via permissive REST routes
Published Jun 9, 2025 · Updated Apr 28, 2026
Authentication bypass in PayU India before 3.8.8 allows remote attackers to take over any WordPress account through public REST APIs. The generate-user-token route returns a token for a hardcoded email, and get-shipping-cost passes the user ID resolved from an attacker-chosen email to update_cart_data, which calls wp_set_auth_cookie. No authentication is required; the resulting session can assume an administrator account.
Summary
What happened
Authentication bypass in PayU India before 3.8.8 allows remote attackers to take over any WordPress account through public REST APIs. The generate-user-token route returns a token for a hardcoded email, and get-shipping-cost passes the user ID resolved from an attacker-chosen email to update_cart_data, which calls wp_set_auth_cookie. No authentication is required; the resulting session can assume an administrator account.
The record
- CVE
- CVE-2025-31022
- Published
- Jun 9, 2025
- Updated
- Apr 28, 2026
- Vendor
- PayU India
- Product
- PayU India
- Classifications
- CWE-288, CAPEC-114, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2025CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.8.8 changes=[{"at":"3.8.8","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Patchstack REST endpoint exploit walkthroughproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo