Code execution via unapproved sensitive-file creation
Published Aug 5, 2025 · Updated Aug 5, 2025
Improper authorization in Cursor before 1.3.9 allows attackers to execute host code through indirect prompt injection. The Agent's file-write guard requires approval to edit an existing dotfile but permits creating a missing .vscode/settings.json, allowing injected settings to change the default shell. Exploitation requires a separate indirect prompt injection that hijacks an active chat context; successful chaining runs code on the host without approval.
Summary
What happened
Improper authorization in Cursor before 1.3.9 allows attackers to execute host code through indirect prompt injection. The Agent's file-write guard requires approval to edit an existing dotfile but permits creating a missing .vscode/settings.json, allowing injected settings to change the default shell. Exploitation requires a separate indirect prompt injection that hijacks an active chat context; successful chaining runs code on the host without approval.
The record
- CVE
- CVE-2025-54130
- Published
- Aug 5, 2025
- Updated
- Aug 5, 2025
- Vendor
- Anysphere
- Product
- Cursor
- Classifications
- CWE-285, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo