dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-59387

HIGH · 8.1 CVSS v4.0 Published 2026-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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 SQL injection vulnerability has been reported to affect MARS (Multi-Application Recovery Service). The remote attackers can then exploit the vulnerability to execute unauthorized code or commands. We have already fixed the vulnerability in the following version: MARS (Multi-Application Recovery Service) 1.2.1.1686 and later

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

SQL injection vulnerability in MARS (Multi-Application Recovery Service) allows remote attackers to inject malicious SQL queries that can lead to unauthorized code or command execution on the underlying system. The vulnerability exists in the application's database interaction layer where user-supplied input is not properly sanitized before being used in SQL statements.

MitigationUpgrade MARS to version 1.2.1.1686 or later to apply the vendor-provided patch. Until then, restrict network access to the MARS service interface and monitor for suspicious database query patterns.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 MARS is installed
    Check common installation directories for MARS executables or services. On Windows, look in Program Files or use 'sc query' to list services containing 'MARS' or 'Multi-Application Recovery'. On Linux, check /opt or /usr/local for mars-related binaries.
    Affected if MARS software is found running on the system
  2. Determine the installed MARS version
    Run 'mars -v' or 'mars --version' from the installation directory, or right-click the executable and select Properties > Details to view the File Version. If MARS runs as a service, check the version via the service properties.
    Affected if The installed version is lower than 1.2.1.1686
  3. Verify if MARS database service is network-accessible
    Check the MARS configuration file (typically mars.conf or database.config in the config directory) for 'bind-address', 'port', or 'listen' settings. Use 'netstat -an | grep <mars_port>' to confirm if the database port is listening on non-loopback interfaces.
    Affected if The MARS database interface listens on 0.0.0.0 or an external IP and is reachable from untrusted networks
  4. Inspect database user permissions
    Review the database connection configuration used by MARS. Check if the application database user has privileges beyond what is required (such as SELECT, INSERT, UPDATE, DELETE only versus administrative or FILE privileges).
    Affected if The MARS database user has elevated privileges that could enable command execution via SQL injection
  5. Review MARS logs for suspicious SQL patterns
    Examine MARS database logs or application logs in the logs/ directory for unusual query patterns, especially those containing SQL operators (UNION, OR, AND) or string literals that might indicate injection attempts.
    Affected if Logs show malformed SQL queries or patterns consistent with injection testing

A user is affected if MARS is installed with a version lower than 1.2.1.1686 and has its database interface network-accessible.

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

Upgrade MARS to version 1.2.1.1686 or later to apply the vendor-provided patch. Until then, restrict network access to the MARS service interface and monitor for suspicious database query patterns.

Recommended fix Moderate confidence

MARS 1.2.1.1686 or later

  1. Identify the current version of QNAP MARS (Multi-Application Recovery Service) installed on the system
  2. If the installed version is earlier than 1.2.1.1686, download MARS version 1.2.1.1686 or later from the official QNAP website
  3. Apply the upgrade following QNAP's standard MARS installation procedures
  4. Verify the installed version is 1.2.1.1686 or later after the upgrade completes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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