dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-52385

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-13
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 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
An issue in Studio 3T v.2025.1.0 and before allows a remote attacker to execute arbitrary code via a crafted payload to the child_process module

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

Studio 3T versions 2025.1.0 and earlier contain a critical remote code execution vulnerability where user-controlled input is passed unsafely to Node.js' child_process module, allowing an attacker to execute arbitrary system commands on the targeted machine.

MitigationApply vendor-supplied patch/upgrade to Studio 3T when available; restrict network access to the application and avoid connecting to untrusted MongoDB servers until patched.

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. Locate Studio 3T installation and version
    Check the installation directory (commonly C:\Program Files\Studio 3T on Windows or /Applications/Studio 3T on macOS). Look for version info in the application properties, about dialog, or the executable file metadata. On Linux, check /opt/studio-3t or the application launcher.
    Affected if The installed version is 2025.1.0 or any earlier version.
  2. Verify if Studio 3T process is running
    Open Task Manager (Windows), Activity Monitor (macOS), or run 'ps aux | grep -i studio' (Linux) to see if Studio 3T is currently active.
    Affected if Studio 3T is running and the version cannot be verified as patched.
  3. Check network exposure of Studio 3T
    Since this is a remote code execution flaw, examine whether Studio 3T has any listener ports exposed to untrusted networks. Use 'netstat -an' or your firewall rules to check for unexpected listening ports associated with Studio 3T.
    Affected if Studio 3T has open network ports accessible from untrusted networks.
  4. Review recent connection logs
    Check Studio 3T connection history or logs for any suspicious MongoDB connections from unknown sources that could have delivered a crafted payload.
    Affected if There are connections from untrusted or unknown sources to Studio 3T.

You are affected if Studio 3T version 2025.1.0 or earlier is installed and running, especially if exposed to network connections.

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

Apply vendor-supplied patch/upgrade to Studio 3T when available; restrict network access to the application and avoid connecting to untrusted MongoDB servers until patched.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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