CVE-2026-64970: Stored XSS in ATutor registration profile phone field
- Vendor
- Atutor
CVE-2026-64970 is a stored cross-site scripting vulnerability in ATutor, confirmed in version 2.2.4, affecting the registration and public profile functionality. An attacker can register a new account and supply a JavaScript payload in the phone field during registration. That value is later rendered in the attacker's public profile without proper output encoding, causing script execution in the browser of an authenticated user who views the profile. The flaw stems from unsafe handling of user-controlled profile data in the profile template and can be used to execute arbitrary script in the victim's session context.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary JavaScript execution in the browser of authenticated users who visit the attacker-controlled public profile. This can lead to theft of session cookies, session hijacking, unauthorized actions performed as the victim, and potential compromise of higher-privileged accounts depending on the victim's role and browser session state.
Mitigation
If you can’t patch tonight, do this now.
If immediate migration is not possible, reduce exposure by disabling or restricting self-registration and public profile access where feasible. Apply custom template-level output encoding or sanitization for profile fields, particularly fields intended to contain plain text such as phone numbers. Limit authenticated users' ability to browse untrusted profiles, monitor for malicious profile content, and consider browser-side defenses such as a restrictive Content Security Policy to reduce XSS exploitability.
Remediation
Patch, then assume compromise.
No official vendor patch is available because ATutor is no longer actively supported. A corrective fix would require proper contextual output encoding of user-controlled profile fields, especially the phone field, before rendering them in profile templates. Additional hardening should include server-side validation of profile input, review of all profile rendering paths for similar unsafe output patterns, and migration to a maintained platform where possible.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-64970 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-64970 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-64970?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-64970.
- Is there a patch for CVE-2026-64970?
- No official vendor patch is available because ATutor is no longer actively supported. A corrective fix would require proper contextual output encoding of user-controlled profile fields, especially the phone field, before rendering them in profile templates.
- What products are affected by CVE-2026-64970?
- Atutor.
- How severe is CVE-2026-64970?
- CVE-2026-64970 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.46% (41st percentile) as of Sep 25, 2026.
Recent activity
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.