Unauthenticated data exposure via server-side requests
Published Nov 13, 2023 · Updated Apr 28, 2026
SSRF in PhonePe Payment Solutions 1.0.15 and earlier allows remote attackers to relay requests through a WordPress site. Public records do not identify the request handler or explain how attacker-controlled destinations reach the server-side HTTP client. No authentication or user interaction is required, and the reported consequence is exposure of data from services reachable by the web server.
Summary
What happened
SSRF in PhonePe Payment Solutions 1.0.15 and earlier allows remote attackers to relay requests through a WordPress site. Public records do not identify the request handler or explain how attacker-controlled destinations reach the server-side HTTP client. No authentication or user interaction is required, and the reported consequence is exposure of data from services reachable by the web server.
The record
- CVE
- CVE-2022-45835
- Published
- Nov 13, 2023
- Updated
- Apr 28, 2026
- Vendor
- PhonePe
- Product
- PhonePe Payment Solutions
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 13, 2023CVE 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 <=1.0.15
- Affected versionversion=n/a <=1.0.15 changes=[{"at":"2.0.0","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
No public exploit references are available in this record.
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