dbcve.org
CmcApplication · Nozominetworks

CVE-2025-40885

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 25.2.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 Smart Polling 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 · high confidence

A SQL Injection vulnerability exists in the Smart Polling functionality where an input parameter lacks proper validation, allowing authenticated low-privilege users to execute arbitrary SELECT queries against the application's database.

MitigationImplement proper input validation and use parameterized queries (prepared statements) for all database queries in the Smart Polling module to prevent SQL injection.

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.2.0
GuardianApplication
Affected:< 25.2.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 product and version
    Locate the installed version of Nozominetworks Cmc or Nozominetworks Guardian in the system documentation or management interface. Compare this version number against the affected range of < 25.2.0.
    Affected if The installed version is Cmc or Guardian and the version number is lower than 25.2.0
  2. Confirm Smart Polling feature is active
    Access the application administration panel or configuration settings and determine whether the Smart Polling module or feature is currently enabled or configured.
    Affected if Smart Polling is enabled or has been configured in the environment
  3. Verify user access to Smart Polling
    Review user account permissions and role assignments to determine if low-privilege authenticated users have access to the Smart Polling functionality.
    Affected if Authenticated users with low-privilege accounts can access or interact with Smart Polling
  4. Inspect Smart Polling input parameters
    Examine the Smart Polling configuration or query interface for any input fields where user-supplied values are used directly in database queries without visible sanitization or parameterized query implementation.
    Affected if User-provided input in Smart Polling is accepted and processed without evident input validation or prepared statement usage
  5. Review database query logs
    Check application or database logs for any anomalous or unexpected SELECT queries originating from Smart Polling operations that may indicate exploitation attempts.
    Affected if Unexpected or arbitrary SELECT queries appear in logs related to Smart Polling activity

A user is affected if their Nozominetworks Cmc or Guardian installation is version 25.2.0 or higher with Smart Polling disabled, or if they are running a version below 25.2.0 with Smart Polling accessible to authenticated users.

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.2.0 or later
Fixed in 25.2.0
Interim mitigation

Implement proper input validation and use parameterized queries (prepared statements) for all database queries in the Smart Polling module to prevent SQL injection.

Recommended fix Moderate confidence

Upgrade Cmc to version 25.2.0 and Guardian to version 25.2.0

  1. Identify the affected product (Cmc or Guardian) currently deployed in your environment
  2. Locate and download the version 25.2.0 release package from the official Nozomi Networks distribution channel
  3. Review the upgrade documentation specific to your product for any prerequisite steps
  4. Perform a backup of the current configuration and database
  5. Execute the upgrade procedure to version 25.2.0 following the documented process
  6. After upgrade, verify the Smart Polling functionality operates correctly
  7. Confirm the application runs without SQL injection errors in logs

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

Fix this in Cmc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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