dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-63705

HIGH · 8.8 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
NPM package node-ts-ocr 1.0.15 is vulnerable to OS Command Injection via the invokeImageOcr function in src/index.js.

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 confidence

The node-ts-ocr NPM package version 1.0.15 is vulnerable to OS Command Injection via the invokeImageOcr function in src/index.js. This allows attackers to execute arbitrary operating system commands by supplying specially crafted input to this function.

MitigationUpgrade to a patched version of node-ts-ocr if available, or refactor invokeImageOcr to use parameterized execution methods instead of shell command invocation, with strict input validation.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Check if node-ts-ocr is installed
    Run 'npm list node-ts-ocr' or inspect package.json dependencies to see if node-ts-ocr is listed as a dependency
    Affected if node-ts-ocr appears in dependencies with version 1.0.15 or an unpatched version
  2. Verify the installed version
    Run 'npm list node-ts-ocr' to display the exact installed version number, or check the version field in node_modules/node-ts-ocr/package.json
    Affected if The installed version is 1.0.15 or falls within any unpatched version range that retains the vulnerable invokeImageOcr function
  3. Inspect the vulnerable function source
    Examine node_modules/node-ts-ocr/src/index.js and locate the invokeImageOcr function to confirm it uses unsafe command invocation (such as exec, spawn, or similar shell execution methods without proper sanitization)
    Affected if The invokeImageOcr function in src/index.js directly passes user input to shell execution APIs without parameterized commands or input validation
  4. Check for usage of invokeImageOcr in your code
    Search your codebase for any calls to invokeImageOcr (for example, using grep or IDE search: 'invokeImageOcr') and review how user-controlled data flows into this function
    Affected if Your application calls invokeImageOcr and passes unsanitized external input to it

You are affected if node-ts-ocr version 1.0.15 (or an unpatched version) is installed and your code uses the invokeImageOcr function with unsanitized input that could be interpreted as 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of node-ts-ocr if available, or refactor invokeImageOcr to use parameterized execution methods instead of shell command invocation, with strict input validation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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