CVE-2025-54132
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 · uneditedCursor is a code editor built for programming with AI. In versions below 1.3, Mermaid (which is used to render diagrams) allows embedding images which then get rendered by Cursor in the chat box. An attacker can use this to exfiltrate sensitive information to a third-party attacker controlled server through an image fetch after successfully performing a prompt injection. A malicious model (or hallucination/backdoor) might also trigger this exploit at will. This issue requires prompt injection from malicious data (web, image upload, source code) in order to exploit. In that case, it can send sensitive information to an attacker-controlled external server. This is fixed in version 1.3.
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 confidenceCursor's Mermaid diagram rendering feature in versions below 1.3 allows embedded images to be fetched and rendered in the chat box. Through prompt injection (via malicious web content, image uploads, or source code), an attacker can trigger the editor to make image fetch requests to attacker-controlled servers, exfiltrating sensitive context such as code, tokens, or conversation data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.3CVSS 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 if Cursor IDE is installedCheck for Cursor application. On macOS, look for /Applications/Cursor.app. On Windows, check Program Files or AppData. On Linux, check for cursor packages via package manager or /usr/bin/cursor.Affected if Cursor IDE is present on the system
-
Determine installed Cursor versionOpen Cursor and navigate to Help > About Cursor (or use command palette and search for 'About Cursor') to view the exact version number.Affected if Version displayed is below 1.3 (for example: 1.0, 1.1, 1.2, 0.x, or any version less than 1.3)
-
Identify Mermaid diagram rendering usageSearch project files and chat history for Mermaid syntax blocks (```mermaid ... ```). Check if the Mermaid feature in Cursor's chat is actively used by reviewing recent conversations or shared diagrams.Affected if Mermaid diagrams are rendered in Cursor's chat interface
-
Check for processing of untrusted inputReview recent workflow: have you pasted content from untrusted websites, uploaded images from external sources, or opened code files from unknown contributors into Cursor? Check clipboard history or recent file imports.Affected if Untrusted web content, image uploads, or source code has been processed in Cursor
User is affected if running any Cursor version below 1.3 AND actively using Mermaid diagram rendering with untrusted or external content that could contain injection payloads
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.
dbcve · scoped1.3
Upgrade Cursor to version 1.3 or later. Additionally, exercise caution when processing untrusted input from web content, image uploads, or source code that could contain prompt injection payloads.
Cursor 1.3
- Check the current version of Cursor by clicking on the Cursor icon or checking Help > About
- Navigate to the Cursor downloads page or use the built-in update mechanism
- Download and install Cursor version 1.3 or later
- Restart Cursor to ensure the update is fully applied
- Verify the version by checking Help > About to confirm version 1.3 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54132 — 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-2025-54132 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