CVE-2024-37405
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLivechat messages can be leaked by combining two NoSQL injections affecting livechat:loginByToken (pre-authentication) and livechat:loadHistory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability chains two NoSQL injection flaws in Livechat components: a pre-authentication injection in livechat:loginByToken combined with an injection in livechat:loadHistory. By exploiting this attack path, an unauthenticated attacker can extract livechat messages from the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Livechat installationLocate the Livechat component in your environment by searching for 'livechat' in installed packages, modules, or application dependencies. Check package.json, requirements.txt, or equivalent dependency files for livechat-related packages.Affected if Livechat component is present in the environment
-
Verify livechat:loginByToken endpoint exposureCheck if the livechat:loginByToken method is accessible without authentication. Review the application routing configuration or API endpoint definitions to determine if this endpoint accepts unauthenticated requests.Affected if The livechat:loginByToken endpoint is accessible to unauthenticated users
-
Verify livechat:loadHistory endpoint exposureExamine the livechat:loadHistory endpoint configuration. Determine whether this endpoint is protected by authentication or if it can be invoked without valid credentials.Affected if The livechat:loadHistory endpoint accepts requests without proper authentication
-
Check for NoSQL database usageIdentify if the backend uses a NoSQL database (such as MongoDB) for storing livechat messages. Review database configuration files or application code that handles livechat data storage.Affected if A NoSQL database stores livechat messages and accepts injection through the identified endpoints
-
Confirm input validation statusReview the code handling livechat:loginByToken and livechat:loadHistory requests. Determine whether input validation or parameterized queries are implemented to sanitize user-supplied data before database queries.Affected if NoSQL injection is possible due to missing input validation on the affected endpoints
The environment is affected if Livechat is installed and the livechat:loginByToken and livechat:loadHistory endpoints are accessible to unauthenticated users without proper input validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper input validation and parameterized queries in both livechat:loginByToken and livechat:loadHistory endpoints to prevent NoSQL injection. Additionally, enforce proper authentication and authorization checks on the loadHistory function.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37405 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data