Unauthorized client enablement via tokenless routes
Published Mar 31, 2025 · Updated Apr 29, 2025
CSRF in Drupal OAuth2 Client before 4.1.3 allows remote attackers to enable a configured OAuth client through a deceived authorized user. The client-enable routes accept state-changing requests without CSRF tokens, so forged requests are processed under the victim's session. Exploitation requires knowledge of the client's machine name and deception of a user permitted to enable clients; the resulting change enables that client.
Summary
What happened
CSRF in Drupal OAuth2 Client before 4.1.3 allows remote attackers to enable a configured OAuth client through a deceived authorized user. The client-enable routes accept state-changing requests without CSRF tokens, so forged requests are processed under the victim's session. Exploitation requires knowledge of the client's machine name and deception of a user permitted to enable clients; the resulting change enables that client.
The record
- CVE
- CVE-2025-31684
- Published
- Mar 31, 2025
- Updated
- Apr 29, 2025
- Vendor
- OAuth.js
- Product
- OAuth2 Client
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 31, 2025CVE publishedPublication date reported by the CVE source.
- Apr 29, 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 <4.1.3
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