dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-27554

CRITICAL · 9.9 CVSS v3.1 Published 2025-03-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
ToDesktop before 2024-10-03, as used by Cursor before 2024-10-03 and other applications, allows remote attackers to execute arbitrary commands on the build server (e.g., read secrets from the desktopify config.prod.json file), and consequently deploy updates to any app, via a postinstall script in package.json. No exploitation occurred.

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 command injection vulnerability in ToDesktop (before 2024-10-03) allows remote attackers to execute arbitrary commands on the build server through a malicious postinstall script in package.json. Attackers can read sensitive secrets from the desktopify config.prod.json file and deploy unauthorized updates to any application using the affected build tool.

MitigationUpdate ToDesktop to version 2024-10-03 or later. Review and rotate any secrets that may have been exposed in the desktopify configuration files, and audit build server logs for signs of unauthorized access.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 ToDesktop installation location
    Search for ToDesktop in common installation directories (e.g., /usr/local/lib/todesktop, %ProgramFiles%\ToDesktop, or check npm global packages with 'npm list -g --depth=0'). Also check for to-desktop CLI with 'which to-desktop' or 'where to-desktop'.
    Affected if ToDesktop is installed on the build server and version cannot be determined or is before 2024-10-03
  2. Determine installed ToDesktop version
    Run 'to-desktop --version' or check the package.json version if ToDesktop is installed as an npm package. Compare the version date or number against 2024-10-03.
    Affected if Version date is before October 3, 2024 or version cannot be determined
  3. Locate config.prod.json file
    Search for config.prod.json in the ToDesktop installation directory, build server working directories, or project folders. Common paths include the project root or .todesktop subdirectory.
    Affected if config.prod.json exists and contains API keys, tokens, or secrets in plaintext
  4. Inspect package.json postinstall scripts
    Review all package.json files in projects built with ToDesktop for postinstall scripts. Look for scripts that execute external commands, download files, or invoke to-desktop CLI with untrusted input.
    Affected if postinstall script executes commands based on unvalidated input or external sources

You are affected if ToDesktop is installed on your build server with a version predating 2024-10-03, or if config.prod.json with secrets is present on the system.

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

Update ToDesktop to version 2024-10-03 or later. Review and rotate any secrets that may have been exposed in the desktopify configuration files, and audit build server logs for signs of unauthorized access.

Recommended fix Moderate confidence

ToDesktop version released on or after 2024-10-03

  1. 1. Identify the ToDesktop dependency in your project's package.json file
  2. 2. Update the ToDesktop package to the latest version using: npm install @todesktop/runtime@latest or npm update @todesktop/runtime
  3. 3. Ensure the update resolves to a version released on or after 2024-10-03
  4. 4. Rebuild your application to incorporate the fixed ToDesktop version
  5. 5. If using Cursor, ensure you update to a version released on or after 2024-10-03 which includes the patched ToDesktop dependency
  6. 6. Verify the build completes successfully and test that the application functions correctly

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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