CVE-2026-64964: Generation of Predictable Email Confirmation Token in ATutor

Published Aug 20, 2026
·
Updated

ATutor generates predictable email confirmation tokens due to the use of insufficiently random values in the account confirmation functionality. Due to the use of predictable values related to user registration, an attacker who knows or can predict these values can guess valid account activation tokens. This allows an attacker to activate an unconfirmed account without access to the victim's email inbox. Product is no longer actively supported and the vulnerabilities have not been fixed. Only version 2.2.4 was tested and confirmed as vulnerable, other versions were not tested but might also be vulnerable.

Affected Software

1 affected component
ATutor ATutor=2.2.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Because ATutor is no longer actively supported and the vulnerability has not been fixed, mitigate by preventing unauthenticated activation via email-confirmation tokens that can be guessed. Restrict/disable the ability for attackers to activate accounts without email inbox access (e.g., limit account activation to paths that require non-guessable proof of email ownership), and monitor/limit new account activations.

Event History

Aug 20, 2026
CVE Published
via MITRE·01:58 PM
Data Sourced
via MITRE·01:58 PM
DescriptionWeakness

Frequently Asked Questions

1

Who is realistically exposed to this issue?

ATutor deployments with unconfirmed user accounts are exposed if they use a vulnerable version. Version 2.2.4 was tested and confirmed vulnerable; other versions were not tested and may also be affected.

2

What does an attacker need to exploit it?

The attacker needs to know or predict the registration-related values used to generate an account activation token. They do not need access to the victim's email inbox.

3

Are patches available?

The product is no longer actively supported, and the vulnerabilities have not been fixed.

4

What should operators do if they cannot patch?

The provided information does not identify a workaround. Operators should treat unconfirmed accounts as at risk of unauthorized activation and review their exposure to vulnerable ATutor versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203