Unauthorized actions via insufficient route CSRF protection
Published May 14, 2025 · Updated May 20, 2025
CSRF in Drupal Restrict route by IP before 1.3.0 allows remote attackers to trigger requests to insufficiently protected routes. The module omits sufficient CSRF defenses on certain routes, but Drupal has not disclosed the route handlers or state-changing operations involved. Exploitation requires user interaction and knowledge of a route machine name; the resulting configuration or data changes are undisclosed.
Summary
What happened
CSRF in Drupal Restrict route by IP before 1.3.0 allows remote attackers to trigger requests to insufficiently protected routes. The module omits sufficient CSRF defenses on certain routes, but Drupal has not disclosed the route handlers or state-changing operations involved. Exploitation requires user interaction and knowledge of a route machine name; the resulting configuration or data changes are undisclosed.
The record
- CVE
- CVE-2025-47701
- Published
- May 14, 2025
- Updated
- May 20, 2025
- Vendor
- OAuth.js
- Product
- Restrict route by IP
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2025CVE publishedPublication date reported by the CVE source.
- May 20, 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