dbcve.org
CmcApplication · Nozominetworks

CVE-2025-40888

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 25.3.0 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A SQL Injection vulnerability was discovered in the CLI functionality due to improper validation of an input parameter. An authenticated user with limited privileges can execute arbitrary SELECT SQL statements on the DBMS used by the web application, potentially exposing unauthorized data.

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

SQL injection vulnerability in the CLI functionality allows authenticated users with limited privileges to execute arbitrary SELECT SQL statements via unsanitized input parameters that are directly concatenated into database queries.

MitigationImplement parameterized queries or prepared statements for all database operations, apply strict input validation and sanitization on CLI input parameters, and enforce least privilege database access for the application accounts.

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
CmcApplication
Affected:< 25.3.0
GuardianApplication
Affected:< 25.3.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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Nozomi product
    Determine whether Nozomi Networks CMC or Guardian is deployed in your environment. Check installed packages, application inventory, or system documentation for the product name.
    Affected if The product is Nozomi Networks CMC or Guardian
  2. Check installed version against threshold
    Locate the installed version of CMC or Guardian using system commands, application logs, or management interface. Compare the version number to 25.3.0.
    Affected if Installed version is lower than 25.3.0
  3. Verify CLI access is enabled
    Check whether CLI functionality is accessible for authenticated users. Review user role permissions and CLI service status in the system configuration.
    Affected if CLI access is enabled and available to authenticated users
  4. Confirm low-privilege user accounts exist
    Review user accounts configured in the system and verify whether accounts with limited privileges (non-admin roles) have CLI access permissions.
    Affected if Low-privilege authenticated users can access CLI functionality

You are affected if CMC or Guardian version is below 25.3.0 and low-privilege authenticated users have access to the CLI interface where unsanitized input flows into database queries.

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
Upgrade available Upgrade to 25.3.0 or later
Fixed in 25.3.0
Interim mitigation

Implement parameterized queries or prepared statements for all database operations, apply strict input validation and sanitization on CLI input parameters, and enforce least privilege database access for the application accounts.

Recommended fix Moderate confidence

25.3.0 or later

  1. Back up the current CMC or Guardian configuration and database before proceeding with the upgrade
  2. Download version 25.3.0 or later from the official Nozomi Networks distribution channel
  3. Consult the official upgrade documentation for CMC or Guardian specific to your deployment type
  4. Execute the upgrade procedure following the documented steps for your product
  5. After upgrade, verify the CLI functionality is operational
  6. Confirm the version number reflects 25.3.0 or later to ensure the fix is applied
  7. Test that the SQL injection vulnerability is mitigated by verifying the affected CLI parameter now properly validates input
Caveat Review release notes for 25.3.0 for any configuration or behavioral changes that may affect your deployment

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

Fix this in Cmc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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