CVE-2025-62354
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 · uneditedImproper neutralization of special elements used in an OS command ('command injection') in Cursor allows an unauthorized attacker to execute commands that are outside of those specified in the allowlist, resulting in arbitrary code execution.
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 · moderate confidenceCursor contains a command injection vulnerability where improper neutralization of special elements in OS command execution allows attackers to bypass an existing allowlist mechanism and execute arbitrary commands on the host system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- 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.
-
Check if Cursor is installedOn Windows: look for Cursor in Program Files or AppData folders. On macOS: check /Applications for Cursor.app. On Linux: check common installation paths like /usr/bin/cursor or ~/.local/share/cursor.Affected if Cursor is found on the system
-
Determine installed Cursor versionOn Windows: right-click Cursor.exe, select Properties, view Details tab for File version. On macOS: right-click Cursor.app, select Get Info, view Version. On Linux: run cursor --version or check the app image metadata.Affected if A version number is retrieved from the Cursor installation
-
Compare version against vulnerable rangeSince no specific CVE version range was provided, compare your installed version against the latest patched version noted in Cursor release notes or security advisories for around 2025.Affected if Your version is older than the patched version and thus potentially vulnerable
-
Identify if command execution feature is in useCursor may have features that execute OS commands (e.g., terminal integration, build/run tasks, extensions that run shell commands). Review Cursor settings.json or check for terminal panels that execute commands.Affected if You use Cursor features that invoke OS commands on the host system
-
Verify allowlist configuration existsThe vulnerability involves bypassing an allowlist for command execution. Check Cursor user settings for any command allowlist, whitelist, or execution policy configurations.Affected if An allowlist or whitelist for commands is configured in Cursor settings
You are affected if you have an older unpatched version of Cursor installed and use its command execution features.
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.
From vendor dataImplement strict input validation and sanitization for all command arguments, ensuring the allowlist enforcement cannot be bypassed. Use parameterized command execution APIs or safe wrapper functions that prevent injection of shell metacharacters.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62354 — 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-62354 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