CVE-2025-54130
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. Cursor allows writing in-workspace files with no user approval in versions less than 1.3.9. If the file is a dotfile, editing it requires approval but creating a new one doesn't. Hence, if sensitive editor files, such as the .vscode/settings.json file don't already exist in the workspace, an attacker can chain a indirect prompt injection vulnerability to hijack the context to write to the settings file and trigger RCE on the victim without user approval. This is fixed in version 1.3.9.
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 versions before 1.3.9 allow writing new files to the workspace without user approval, including dotfiles like .vscode/settings.json (creating new dotfiles doesn't require approval, though editing existing ones does). When chained with indirect prompt injection, an attacker can hijack the AI context to write malicious content to settings.json and achieve remote code execution without any user approval.
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.3.9CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the installed Cursor versionOpen Cursor, then navigate to Help > About (or use the command palette with Cmd/Ctrl+Shift+P and search for 'About'). The version number is displayed in the dialog that opens.Affected if The displayed version number is less than 1.3.9 (for example, 1.3.8, 1.3.7, 1.3.6, etc.)
-
Verify version via command line (optional)Run 'cursor --version' in a terminal, or on macOS check /Applications/Cursor.app/Contents/Info.plist for CFBundleShortVersionString, or on Windows check the executable properties.Affected if The version returned is less than 1.3.9
-
Confirm the write permission behavior (if testing safely)Ask Cursor's AI assistant to create a new file in the workspace, such as a test file like 'test-write-123.txt' or a dotfile like '.test-dotfile'. Observe whether a user approval prompt appears before the file is written.Affected if The AI writes a new file without presenting an approval dialog (no user consent is requested).
You are affected if your installed Cursor version is lower than 1.3.9, as this version range permits the AI to write new files including dotfiles to the workspace without user approval.
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.9
Upgrade Cursor to version 1.3.9 or later to remediate this vulnerability.
Cursor version 1.3.9 or later
- Ensure Cursor is not currently running
- Check your current Cursor version by clicking on Cursor in the menu and selecting 'About Cursor' or similar
- Navigate to the official Cursor download page at cursor.sh or check for updates within the application
- Download Cursor version 1.3.9 or later
- Install the new version, which will overwrite the existing installation
- Restart Cursor after the upgrade completes
- Verify the new version is installed by checking 'About Cursor'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54130 — 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-54130 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