Authenticated 2FA bypass via manipulated API responses
Published Feb 14, 2025 · Updated Feb 14, 2025
Authentication bypass in RupeeWeb before 66.9 allows remote authenticated users to bypass 2FA for other accounts via API response manipulation. Certain API endpoints trust attacker-modified response data during OTP validation instead of treating that data as untrusted. Valid platform credentials are required, and successful exploitation defeats the second authentication factor protecting another account.
Summary
What happened
Authentication bypass in RupeeWeb before 66.9 allows remote authenticated users to bypass 2FA for other accounts via API response manipulation. Certain API endpoints trust attacker-modified response data during OTP validation instead of treating that data as untrusted. Valid platform credentials are required, and successful exploitation defeats the second authentication factor protecting another account.
The record
- CVE
- CVE-2025-26522
- Published
- Feb 14, 2025
- Updated
- Feb 14, 2025
- Vendor
- Rupeeseed Technology Ventures
- Product
- RupeeWeb
- Classifications
- CWE-302, T1556.006
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 14, 2025Record 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=<66.9
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