Authentication bypass via forged auto-login token
Published Aug 20, 2026 · Updated Aug 20, 2026
Authentication bypass in ATutor 2.2.4 allows remote attackers to log in as any user via a forged auto-login token. In the auto-login functionality, token validation can execute with uninitialized values, so a token derived from a target user's identifier and registration timestamp is accepted as valid. Exploitation requires knowing or deriving those two user attributes; if the chosen account is an administrator, the attacker gains full administrative access without the password.
Summary
What happened
Authentication bypass in ATutor 2.2.4 allows remote attackers to log in as any user via a forged auto-login token. In the auto-login functionality, token validation can execute with uninitialized values, so a token derived from a target user's identifier and registration timestamp is accepted as valid. Exploitation requires knowing or deriving those two user attributes; if the chosen account is an administrator, the attacker gains full administrative access without the password.
The record
- CVE
- CVE-2026-64961
- Published
- Aug 20, 2026
- Updated
- Aug 20, 2026
- Vendor
- ATutor
- Product
- ATutor
- Classifications
- CWE-639, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 20, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=2.2.4
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