LiveActive security incident?Get immediate response
CVE Record

CVE-2024-54999: MonicaHQ v4.1.2 was discovered to contain a Client-Side Injection vulnerability via the last_name parameter...

MonicaHQ v4.1.2 was discovered to contain a Client-Side Injection vulnerability via the last_name parameter the General Information module.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

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.
Prepared
Confidence
medium
Sources
3

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-54999 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N3.92.5CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2024-54999Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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.