dbcve.org
CursorApplication · Anysphere

CVE-2025-54133

CRITICAL · 9.6 CVSS v3.1 Published 2025-08-02
Fix available
A fix is available. Upgrade to 1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Cursor is a code editor built for programming with AI. In versions 1.17 through 1.2, there is a UI information disclosure vulnerability in Cursor's MCP (Model Context Protocol) deeplink handler, allowing attackers to execute 2-click arbitrary system commands through social engineering attacks. When users click malicious `cursor://anysphere.cursor-deeplink/mcp/install` links, the installation dialog does not show the arguments being passed to the command being run. If a user clicks a malicious deeplink, then examines the installation dialog and clicks through, the full command including the arguments will be executed on the machine. 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 confidence

A UI information disclosure vulnerability in Cursor's MCP deeplink handler (versions 1.17-1.2) allows malicious cursor://anysphere.cursor-deeplink/mcp/install links to bypass argument visibility in the installation dialog. Attackers can exploit this 2-click social engineering vector to execute arbitrary system commands without users seeing the full command being approved.

MitigationUpgrade Cursor to version 1.3 or later. Until patched, users must avoid clicking untrusted cursor:// deeplinks and carefully inspect any installation prompts for hidden command arguments.

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
CursorApplication
Affected:>= 1.1.7, < 1.3

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 checks

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

  1. Identify installed Cursor version
    Open Cursor, go to Help > About, or run 'cursor --version' from command line if available. The version number is displayed in the format like 1.2.0, 1.1.8, etc.
    Affected if The displayed version is 1.1.7 or any version from 1.1.8 through 1.2.x (anything >= 1.1.7 but < 1.3)
  2. Confirm MCP deeplink handling is enabled
    Check if Cursor has ever processed a cursor://anysphere.cursor-deeplink/mcp/install link. Review browser history or application logs for any cursor:// URL clicks, particularly those containing '/mcp/install'
    Affected if Such deeplinks have been clicked and Cursor processed an MCP installation request while showing a dialog
  3. Inspect recent MCP installation dialogs
    Review any recent MCP-related installation prompts you have seen. Verify whether the full command arguments were visible in the installation dialog or if the arguments field appeared obscured or truncated
    Affected if The dialog did not display the complete command arguments, showing only partial or hidden parameters to the user
  4. Check for unexpected system command executions
    Review system command history, shell logs, or security audit logs around the time of any MCP installation prompts. Look for commands that correspond to MCP installations that you do not recognize
    Affected if Arbitrary system commands were executed that were not explicitly authorized or visible during the approval process

You are affected if your Cursor version is 1.1.7 through 1.2.x (any version >= 1.1.7 but < 1.3) and you have clicked on untrusted cursor:// deeplinks that triggered MCP installation dialogs with hidden arguments.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.3 or later
Fixed in 1.3
Interim mitigation

Upgrade Cursor to version 1.3 or later. Until patched, users must avoid clicking untrusted cursor:// deeplinks and carefully inspect any installation prompts for hidden command arguments.

Recommended fix High confidence

Cursor 1.3

  1. Open Cursor and navigate to Help > Check for Updates to check current version
  2. If an update to version 1.3 or later is available, click to download and install it
  3. Alternatively, download Cursor version 1.3 or later directly from the official Cursor website (cursor.sh)
  4. Run the installer and follow the prompts to complete the upgrade
  5. Restart Cursor after the installation completes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cursor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54133 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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