Security readout for executives and security teams
Plain-English summary
CVE-2024-54999 is a medium-severity client-side injection issue reported in MonicaHQ v4.1.2. The reported input point is the last_name parameter in the General Information module. Business risk is mainly unauthorized script execution in a user’s browser, which could affect confidentiality and integrity, but the public record does not name active exploitation or a vendor fix.
Executive priority
Treat as a near-term application security task, not an emergency unless MonicaHQ is internet-facing or stores sensitive relationship data. Prioritize inventory, vendor guidance, and upgrade planning.
Technical view
The CVE describes client-side injection via the last_name parameter in MonicaHQ v4.1.2’s General Information module. NVD-style data in the bundle lists CVSS 3.1 score 6.5, AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N, and CWE-94. Available sources do not provide confirmed patched versions, detailed impact analysis, or exploitation-in-the-wild evidence.
Likely exposure
Organizations running MonicaHQ v4.1.2 are the identified exposure group. The source bundle does not confirm other affected versions, hosted deployments, or package variants.
Exploitation context
The CVE is not listed as KEV in the provided data. Public information supports a reported vulnerability and proof reference, but not active exploitation. Because the vector is network-accessible and low complexity, exposed MonicaHQ instances should still be reviewed promptly.
Researcher notes
Evidence is limited to the CVE entry and a GitHub reference. The CVE labels this CWE-94, but the description says client-side injection, so classification may need vendor or CNA clarification. Do not assume affected versions beyond v4.1.2 from the supplied sources.
Mitigation direction
Identify any MonicaHQ v4.1.2 deployments in production or test environments.
Check MonicaHQ project or maintainer guidance for a fixed version or workaround.
Restrict access to MonicaHQ where feasible until vendor guidance is confirmed.
Review input handling and output encoding around profile General Information fields.
Validation and detection
Confirm installed MonicaHQ versions through asset inventory or application metadata.
Review whether the General Information last_name field is reachable by untrusted users.
Check application logs for unusual profile-field changes or suspicious rendered content.
Track the CVE record and referenced GitHub page for updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.