Cyber Resilience

CVE-2024-32484

XSS in Ankitects Anki 24.04

Public PoCXSS
Published
22 July 2024
Modified
04 November 2025
CVSS Score v3.1 7.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS Score 0.26 98th percentile
Risk Priority 68 floored blend · peak EPSS

Summary

CVE-2024-32484 is a high-severity Basic XSS (CWE-80) vulnerability in Ankitects Anki. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-32484 is a reflected cross-site scripting vulnerability in the Flask server component of Ankitects Anki version 24.04. The flaw arises during handling of invalid paths and is assigned CWE-79 and CWE-80. A specially crafted flashcard can cause JavaScript execution that results in arbitrary file read, with a CVSS 3.1 score of 7.4 reflecting network attack vector, low complexity, no required privileges, required user interaction, changed scope, and high confidentiality impact.

An attacker can exploit the issue by sharing a malicious flashcard with a victim. When the victim interacts with the card, the reflected XSS payload executes in the browser, enabling the attacker to read arbitrary files from the victim's system.

The EPSS score remains flat at 0.0718 with no material increase after disclosure. The primary reference is the Talos Intelligence advisory TALOS-2024-1995.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An reflected XSS vulnerability exists in the handling of invalid paths in the Flask server in Ankitects Anki 24.04. A specially crafted flashcard can lead to JavaScript code execution and result in an arbitrary file read. An attacker can share…

more

a malicious flashcard to trigger this vulnerability.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-34033Shared CWE-79, CWE-80
CVE-2024-49337Shared CWE-79, CWE-80
CVE-2024-45406Shared CWE-79, CWE-80
CVE-2023-47869Shared CWE-79, CWE-80
CVE-2024-37732Shared CWE-79, CWE-80
CVE-2025-25299Shared CWE-79, CWE-80
CVE-2024-6052Shared CWE-79, CWE-80
CVE-2023-30615Shared CWE-79, CWE-80
CVE-2023-20257Shared CWE-79, CWE-80
CVE-2024-42195Shared CWE-79, CWE-80

Affected Assets

ankitects
anki
24.04

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2
  • V1.2.1
  • V1.3.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover missing or incorrect neutralization of script tags through targeted XSS test cases.

Input validation explicitly requires checking and neutralizing untrusted web inputs containing script-related characters before they reach a downstream renderer.

Output filtering can catch or sanitize unneutralized script content before it is served to users.

Secure engineering principles include mandatory output encoding and neutralization of HTML metacharacters to stop injection at the source.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require output encoding and input validation that prevent basic XSS.

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches unneutralized script tags before release.

prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

prevents

Secure SDLC mandates input validation and output encoding that directly prevent basic XSS.

prevents

Application security requirements explicitly call for neutralization of script-related HTML tags.

prevents

Secure coding standards require proper escaping of <, >, & to block XSS.

References