dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-49150

MEDIUM · 5.9 CVSS v3.1 Published 2025-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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. Prior to 0.51.0, by default, the setting json.schemaDownload.enable was set to True. This means that by writing a JSON file, an attacker can trigger an arbitrary HTTP GET request that does not require user confirmation. Since the Cursor Agent can edit JSON files, this means a malicious agent, for example, after a prompt injection attack already succeeded, could trigger a GET request to an attacker controlled URL, potentially exfiltrating other data the agent may have access to. This vulnerability is fixed in 0.51.0.

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

In Cursor versions prior to 0.51.0, the default setting json.schemaDownload.enable allowed arbitrary HTTP GET requests when editing JSON files without user confirmation. An attacker with agent control (e.g., via prompt injection) could trigger requests to attacker-controlled URLs to exfiltrate sensitive data accessible to the Cursor Agent.

MitigationUpgrade Cursor to version 0.51.0 or later, and audit logs for any suspicious outbound HTTP requests that may indicate exploitation.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Verify Cursor version
    Check the installed Cursor version in the application (usually found in Help > About or the app settings) and compare it against the affected range: versions prior to 0.51.0
    Affected if The installed version is older than 0.51.0
  2. Inspect json.schemaDownload.enable setting
    Access Cursor settings and locate the json.schemaDownload.enable configuration option. This is typically found in the JSON schema settings or user preferences file.
    Affected if The setting json.schemaDownload.enable is set to true or enabled (the summary indicates it was enabled by default)
  3. Review network logs for suspicious outbound requests
    Examine Cursor process network connections and any available application logs for HTTP GET requests that occurred during JSON file editing, particularly to unfamiliar or attacker-controlled domains.
    Affected if Outbound HTTP requests to unknown URLs are present in logs and were initiated during JSON editing sessions
  4. Audit for prompt injection or agent compromise
    Review conversation history or input handling for the Cursor Agent to identify any potential prompt injection attempts that could have triggered unauthorized schema downloads.
    Affected if There are signs of prompt injection or unauthorized agent commands that could have triggered the vulnerable feature

A user is affected if they are running Cursor versions prior to 0.51.0 with the json.schemaDownload.enable setting enabled, and particularly if they have engaged with potentially injected prompts that could trigger outbound HTTP requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cursor to version 0.51.0 or later, and audit logs for any suspicious outbound HTTP requests that may indicate exploitation.

Recommended fix High confidence

Cursor version 0.51.0 or later

  1. Open Cursor and check the current version (usually found in the app menu or about section)
  2. If an update is available, use Cursor's built-in auto-update feature to upgrade to version 0.51.0 or later
  3. Alternatively, download the latest version from the official Cursor website (cursor.sh) and install it
  4. After upgrading, verify that json.schemaDownload.enable is set to false (or that the default has changed) by checking Cursor settings

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49150 — 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-49150 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