dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-61141

HIGH · 7.5 CVSS v3.1 Published 2025-10-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
sqls-server/sqls 0.2.28 is vulnerable to command injection in the config command because the openEditor function passes the EDITOR environment variable and config file path to sh -c without sanitization, allowing attackers to execute arbitrary commands.

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

sqls-server/sqls 0.2.28 contains a command injection vulnerability in the config command. The openEditor function passes the EDITOR environment variable and config file path directly to sh -c without sanitization, allowing attackers who control the EDITOR variable to inject arbitrary shell commands.

MitigationSanitize or properly escape the EDITOR environment variable and config file path before passing to shell commands, or avoid shell execution by using execve-style calls with explicit arguments instead of sh -c.

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Identify sqls version
    Run 'sqls --version' or check the installed binary/package version
    Affected if version is 0.2.28 exactly or falls within a range including 0.2.28 without a fix applied
  2. Check EDITOR environment variable
    Run 'echo $EDITOR' to see if the EDITOR variable is set
    Affected if EDITOR is set to any value, especially if it can be controlled by untrusted users or processes
  3. Verify config command availability
    Run 'sqls help config' or check if the config subcommand exists
    Affected if the config command is available and executable in the installed version
  4. Inspect process environment for EDITOR exposure
    Check '/proc/<sqls_pid>/environ' or use 'env | grep EDITOR' while sqls is running
    Affected if EDITOR variable is present in the environment where sqls executes

If sqls version 0.2.28 is installed and the EDITOR environment variable is set (especially if accessible to other users or processes), the environment is vulnerable to command injection via the config command.

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

Sanitize or properly escape the EDITOR environment variable and config file path before passing to shell commands, or avoid shell execution by using execve-style calls with explicit arguments instead of sh -c.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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