Enrollment changes via insufficiently protected routes
Published Jun 26, 2025 · Updated Jun 26, 2025
CSRF in Drupal Open Social before 12.3.14 and 12.4.0 through 12.4.12 allows remote attackers to alter event enrollments. The default event-enrollment module accepts state-changing enrollment acceptance or rejection requests on routes without sufficient CSRF protection. Exploitation requires event enrollments to be enabled for an event and an authenticated user to be tricked into sending the forged request.
Summary
What happened
CSRF in Drupal Open Social before 12.3.14 and 12.4.0 through 12.4.12 allows remote attackers to alter event enrollments. The default event-enrollment module accepts state-changing enrollment acceptance or rejection requests on routes without sufficient CSRF protection. Exploitation requires event enrollments to be enabled for an event and an authenticated user to be tricked into sending the forged request.
The record
- CVE
- CVE-2025-48921
- Published
- Jun 26, 2025
- Updated
- Jun 26, 2025
- Vendor
- OAuth.js
- Product
- Open Social
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2025CVE publishedPublication date reported by the CVE source.
- Jun 26, 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 <12.3.14
- Affected versionversion=12.4.0 <12.4.13
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