Command InjectionWeakness · CWE-77

CVE-2024-48142

HIGH · 7.5 CVSS v3.1 Published 2024-10-24

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

84/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

A prompt injection vulnerability in the chatbox of Butterfly Effect Limited Monica ChatGPT AI Assistant v2.4.0 allows attackers to access and exfiltrate all previous and subsequent chat data between the user and the AI assistant via a crafted message.

Technical summary

dbcve analysis · moderate confidence

A prompt injection vulnerability in the chatbox of Monica ChatGPT AI Assistant v2.4.0 allows attackers to send crafted messages that cause the AI to leak previous conversation history and capture subsequent messages, enabling exfiltration of sensitive chat data between users and the assistant.

MitigationImplement robust input validation and sanitization for user messages before they're processed by the AI model, combined with output filtering and context isolation mechanisms to prevent prompt injection attacks from manipulating the AI's behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if Monica ChatGPT AI Assistant is installed

Check system for Monica ChatGPT AI Assistant application installation - look for the application in installed programs, browser extensions, or desktop application directories. Common locations: Program Files (Windows), Applications folder (Mac), or browser extension manager.

Affected if Monica ChatGPT AI Assistant software is found on the system
Determine the installed version number

Locate the application and check its version. For desktop app: Right-click the application, select Properties, and look at the Details tab for version info. For browser extension: Open browser extension settings and view the version details. Compare against v2.4.0 and any other versions released around this timeframe.

Affected if Installed version matches or falls within the v2.4.0 release cycle (verify against official release notes if available)
Verify the chatbox feature is accessible

Launch the Monica ChatGPT AI Assistant application and confirm the chatbox interface is available and functional. The chatbox is the primary input method for sending messages to the AI assistant.

Affected if The chatbox feature is present and operational in the application
Confirm the application processes user messages

Use the chatbox to send a test message and verify the AI assistant processes and responds to it. This confirms the vulnerable input pathway is active.

Affected if User messages are processed through the chatbox to the AI model
Check for evidence of conversation history storage

Examine if the application stores or displays previous conversation history within the chat interface. The vulnerability allows exfiltration of this stored history.

Affected if Conversation history is visible or stored within the application session

A user is affected if Monica ChatGPT AI Assistant v2.4.0 is installed with the chatbox feature enabled and actively processing messages, as this is the vulnerable pathway for prompt injection.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement robust input validation and sanitization for user messages before they're processed by the AI model, combined with output filtering and context isolation mechanisms to prevent prompt injection attacks from manipulating the AI's behavior.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-48142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-48142 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-48142?

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.

What this is

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.

What belongs here

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

At a glance

A fix existsA vendor remedy is published

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.4%

Remediation

A high-priority fix

Have this fixed 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-48142 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References