Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-54996 is a high-severity Cross-site Scripting (CWE-79) vulnerability in Monicahq Monica. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 43% 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-54996 is a high-severity vulnerability (CVSS 3.1 score of 8.8) affecting MonicaHQ version 4.1.2, an open-source personal relationship management tool. The flaw involves multiple authenticated client-side injection vulnerabilities, mapped to CWE-79 (Cross-Site Scripting) and CWE-94 (Code Injection), exploitable through the title and description parameters in the endpoint /people/ID/reminders/create. These injections occur on the client side, potentially allowing malicious payloads to execute in the victim's browser context.
An attacker with low-privilege authenticated access (PR:L), such as a registered user, can exploit this by submitting crafted title or description inputs when creating reminders for a person profile. Successful exploitation enables high-impact confidentiality, integrity, and availability violations (C:H/I:H/A:H), including theft of session data, manipulation of user data, or disruption of application functionality, all over the network (AV:N) with low complexity (AC:L) and no additional user interaction required (UI:N) beyond normal application use.
Advisories and related resources are available at the official MonicaHQ site (http://monicahq.com) and a GitHub repository containing proof-of-concept details (https://github.com/p314dO/CVEs/tree/main/CVE-2024-54996), published on 2025-01-10. Practitioners should review these for patch availability or workarounds in MonicaHQ updates.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-52721
Vulnerability Data
MonicaHQ v4.1.2 was discovered to contain multiple authenticated Client-Side Injection vulnerabilities via the title and description parameters at /people/ID/reminders/create.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.1.2V1.3.2V1.3.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect input neutralization through targeted web-application tests.
Input validation directly enforces neutralization of untrusted data before it reaches web output generation.
Output filtering can catch or sanitize unneutralized script content before it is served to users.
Least privilege limits the damage an injected code fragment can perform once executed.
Requiring documented secure development standards and tools enforces use of safe code-generation APIs and escaping.
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.
Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).
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.
Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.
Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.