Forced logout via unprotected CSRF route
Published Mar 26, 2026 · Updated Mar 26, 2026
CSRF in Drupal Automated Logout before 1.7.0 and 2.0.0 through 2.0.1 allows remote attackers to force authenticated users to log out. The module's logout route accepts a session-bearing cross-site request without validating a CSRF token, causing the victim's session to terminate. An authenticated Drupal session must load attacker-controlled content, and the consequence is limited to forced session termination without reported data access or modification.
Summary
What happened
CSRF in Drupal Automated Logout before 1.7.0 and 2.0.0 through 2.0.1 allows remote attackers to force authenticated users to log out. The module's logout route accepts a session-bearing cross-site request without validating a CSRF token, causing the victim's session to terminate. An authenticated Drupal session must load attacker-controlled content, and the consequence is limited to forced session termination without reported data access or modification.
The record
- CVE
- CVE-2026-4393
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- Avatar Uploader Project
- Product
- Automated Logout
- Classifications
- CWE-352, CAPEC-62
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 2026Record 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.7.0
- Affected versionversion=2.0.0 <2.0.2
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