dbcve.org
Runzero PlatformApplication · Runzero

CVE-2026-5372

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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 that allowed a SQL injection attack vector related to saved queries (introduced in version 4.0.260123.0). This is an instance of CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'), and has an estimated CVSS score of CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H (6.4 Medium). This issue was fixed in version 4.0.260123.1 of the runZero Platform.

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 the runZero Platform's saved queries feature (introduced in version 4.0.260123.0). Attackers with high privileges could inject malicious SQL commands through saved queries, potentially compromising confidentiality, integrity, and availability of the database.

MitigationUpgrade to runZero Platform version 4.0.260123.1 or later to patch the SQL injection vulnerability in saved queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Runzero PlatformApplication
Affected:= 4.0.260123.0

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
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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 installed runZero Platform version
    Access the platform's administration interface or check system information to determine the currently installed version number
    Affected if The installed version is exactly 4.0.260123.0
  2. Verify saved queries feature is in use
    Check if any saved queries have been created in the platform by reviewing the saved queries configuration or database records
    Affected if Saved queries exist in the system and the platform version is 4.0.260123.0
  3. Audit user privileges
    Review user accounts and their privilege levels, specifically looking for accounts with high privileges that could execute saved queries
    Affected if High-privilege accounts exist on the platform version 4.0.260123.0 with saved queries enabled
  4. Inspect database for anomalous SQL activity
    Review database logs or audit trails for unexpected or unauthorized SQL commands being executed, particularly those originating from saved query executions
    Affected if Suspicious SQL commands appear in logs related to saved queries on the affected version

A system is affected if it runs runZero Platform version 4.0.260123.0 with the saved queries feature enabled and high-privilege users present.

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 to runZero Platform version 4.0.260123.1 or later to patch the SQL injection vulnerability in saved queries.

Recommended fix High confidence

4.0.260123.1

  1. Backup your runZero Platform configuration and data before upgrading
  2. Download the fixed version 4.0.260123.1 from the official runZero download portal or management console
  3. Upgrade your runZero Platform instance from version 4.0.260123.0 to version 4.0.260123.1 following the standard upgrade procedure
  4. After upgrade, verify the version number reflects 4.0.260123.1 in the platform settings
  5. Test that saved queries functionality works correctly post-upgrade to confirm the SQL injection fix is applied

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

Fix this in Runzero Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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