Authenticated TFA bypass via REST login routes
Published May 21, 2025 · Updated May 21, 2025
Authentication bypass in Drupal One Time Password before 1.3.0 allows remote authenticated users to skip TFA through REST login routes. The REST login path accepts valid primary credentials without sufficiently applying the module's TFA enforcement, leaving that alternate channel outside the second-factor gate. A valid username and password are required; successful exploitation grants the affected account's authenticated access without a TOTP challenge.
Summary
What happened
Authentication bypass in Drupal One Time Password before 1.3.0 allows remote authenticated users to skip TFA through REST login routes. The REST login path accepts valid primary credentials without sufficiently applying the module's TFA enforcement, leaving that alternate channel outside the second-factor gate. A valid username and password are required; successful exploitation grants the affected account's authenticated access without a TOTP challenge.
The record
- CVE
- CVE-2025-48011
- Published
- May 21, 2025
- Updated
- May 21, 2025
- Vendor
- OAuth.js
- Product
- One Time Password
- Classifications
- CWE-288, CAPEC-554, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 21, 2025CVE publishedPublication date reported by the CVE source.
- May 21, 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=0.0.0 <1.3.0
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