CVE-2024-48140
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 · uneditedA prompt injection vulnerability in the chatbox of Butterfly Effect Limited Monica Your AI Copilot powered by ChatGPT4 v6.3.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 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 · high confidenceA prompt injection vulnerability in the chatbox of Butterfly Effect Limited Monica Your AI Copilot powered by ChatGPT4 v6.3.0 allows attackers to send crafted messages that manipulate the AI assistant into revealing all previous and subsequent chat data between users and the AI, enabling data exfiltration of conversation history.
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
- 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? 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 installed version of Monica Your AI CopilotAccess the application settings or 'About' section within the Monica Your AI Copilot desktop or web interface to locate the current software version numberAffected if The installed version matches exactly 6.3.0, as this is the only confirmed affected version in the provided advisory
-
Confirm chatbox feature is activeVerify that the chat conversation interface is accessible and functional - check if users can send and receive messages through the AI assistantAffected if The chatbox feature is enabled and users can interact with the AI, as this is the attack surface for the prompt injection vulnerability
-
Test for prompt injection susceptibilitySend a carefully crafted prompt injection message through the chatbox that attempts to override system instructions or request disclosure of conversation history (e.g., a message designed to make the AI ignore its prior instructions or reveal past chats)Affected if The AI assistant responds to the injection attempt by revealing conversation history, ignoring its system instructions, or behaving in a manner inconsistent with its configured behavior, confirming the vulnerability is present
-
Review conversation history access controlsCheck if there are any configuration settings or access controls that limit the AI's ability to reference or retrieve previous conversation dataAffected if There are no meaningful access controls or conversation boundary controls configured, allowing an injected prompt to access all chat history
A user is affected if they are running Monica Your AI Copilot version 6.3.0 with the chatbox feature enabled and the AI can be manipulated through prompt injection to reveal conversation history.
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 input validation and output filtering to detect and block prompt injection patterns; strengthen system prompt instructions to prevent instruction override; consider adding conversation boundary controls to limit the scope of injected commands.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48140 — 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-48140 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