# CVE-2025-54132: Cursor's Mermaid Diagram Tool is Vulnerable to an Arbitrary Image Fetch

> Attackers can exfiltrate sensitive data to external servers via malicious image fetches in Mermaid diagrams, requiring prompt injection.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2025
- **Updated:** 4 Aug 2025

## What is CVE-2025-54132?

CVE-2025-54132 is a medium-severity server-side request forgery vulnerability in cursor, published on 1 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cursor 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-54132?

It affects 1 product.


Products: Anysphere Cursor.

## How do I fix CVE-2025-54132?

No fix has been published for CVE-2025-54132 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-54132 being exploited?

There is no known exploitation of CVE-2025-54132 in the wild and no public exploit code.

## Other vulnerabilities in cursor

- [CVE-2026-50548](https://insights.sbomify.com/CVE-2026-50548/): Cursor Desktop sandbox escape via agent-controlled working directory (critical 9.3)
- [CVE-2026-50549](https://insights.sbomify.com/CVE-2026-50549/): Cursor Desktop sandbox escape via symlink and failed path canonicalization (critical 9.3)
- [CVE-2025-64106](https://insights.sbomify.com/CVE-2025-64106/): Cursor: Speedbump Modal Bypass in MCP Server Deep-Link (high 8.8)
- [CVE-2025-64107](https://insights.sbomify.com/CVE-2025-64107/): Cursor is Vulnerable to Path Manipulation Using Backslashes on Windows (high 8.8)
- [CVE-2025-64108](https://insights.sbomify.com/CVE-2025-64108/): Cursor's Sensitive File Modification can Lead to NTFS Path Quirks (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54132 and fix it if it is affected.

What it is: CVE-2025-54132 is a medium-severity server-side request forgery vulnerability in cursor, published on 1 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54132 in the wild and no public exploit code.

Affected product: cursor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54132/ (Markdown: https://insights.sbomify.com/CVE-2025-54132/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54132
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54132
- OSV: https://osv.dev/vulnerability/CVE-2025-54132

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54132/
Summaries are generated and may contain mistakes; the official description above is the record.