dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-55294

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
screenshot-desktop allows capturing a screenshot of your local machine. This vulnerability is a command injection issue. When user-controlled input is passed into the format option of the screenshot function, it is interpolated into a shell command without sanitization. This results in arbitrary command execution with the privileges of the calling process. This vulnerability is fixed in 1.15.2.

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

The screenshot-desktop library contains a command injection vulnerability where user-controlled input to the format parameter is directly interpolated into a shell command without sanitization, allowing arbitrary command execution with the privileges of the calling process.

MitigationUpgrade the screenshot-desktop package to version 1.15.2 or later to obtain the patched version.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if screenshot-desktop is installed
    Run 'npm list screenshot-desktop' or check package.json for screenshot-desktop in dependencies
    Affected if screenshot-desktop appears in installed dependencies
  2. Check the installed version
    Compare the installed version number to the affected range (versions prior to 1.15.2)
    Affected if Installed version is lower than 1.15.2 (e.g., 1.15.0, 1.14.0, etc.)
  3. Identify usage of the format parameter in screenshot-desktop
    Search project source code for calls to screenshot-desktop functions that accept a format parameter (e.g., screenshot(), captureDesktop())
    Affected if Code passes a format parameter to screenshot-desktop functions
  4. Verify if format input is user-controlled
    Inspect the code path that supplies the format value - check if it comes from user input, HTTP requests, environment variables, or other untrusted sources
    Affected if The format parameter value originates from user input, request parameters, or untrusted sources without validation
  5. Confirm shell command execution with format parameter
    Review code to determine if the format value is passed to a shell execution function (exec(), spawn(), execSync()) without sanitization or use of shell option
    Affected if The format parameter flows directly to a shell execution without passing shell:false or validating the input

You are affected if screenshot-desktop version is below 1.15.2 AND your code passes an untrusted format parameter to screenshot-desktop functions that execute shell commands.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade the screenshot-desktop package to version 1.15.2 or later to obtain the patched version.

Recommended fix High confidence

1.15.2

  1. Identify the current version of screenshot-desktop in your project by running `npm list screenshot-desktop` or checking package.json
  2. Upgrade to version 1.15.2 or later by running `npm install screenshot-desktop@^1.15.2`
  3. Verify the upgrade was successful by running `npm list screenshot-desktop` to confirm the installed version
  4. Rebuild and redeploy your application to ensure the fixed version is used in production
  5. Review your codebase to ensure no user-controlled input is passed to the format option of the screenshot function, as a defense-in-depth measure

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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