dbcve.org
CmcApplication · Nozominetworks

CVE-2025-40887

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 Alert 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

A SQL Injection vulnerability exists in the Alert functionality due to improper input validation. An authenticated user with limited privileges can inject arbitrary SELECT SQL statements through an unvalidated input parameter, potentially exposing sensitive database information.

MitigationImplement parameterized queries (prepared statements) or proper input validation and sanititization for all input parameters in the Alert functionality to prevent SQL injection attacks.

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. Check installed CMC version
    Access the CMC administration interface or run the command: 'cmc --version' or check the software release information in the system. For appliance deployments, check '/opt/cmc/version' or the about page in the web UI.
    Affected if The version is lower than 25.2.0 (e.g., 25.1.x, 25.0.x, or earlier)
  2. Check installed Guardian version
    Access the Guardian administration interface or run the command: 'guardian --version' or check the software release information in the system. For appliance deployments, check '/opt/guardian/version' or the about page in the web UI.
    Affected if The version is lower than 25.2.0 (e.g., 25.1.x, 25.0.x, or earlier)
  3. Determine if Alert functionality is configured
    Navigate to the Alert configuration section in the CMC or Guardian web interface. Check if any alert rules, alert profiles, or alert notifications are defined or enabled.
    Affected if Any alert rules or alert configurations exist in the system
  4. Check for unusual alert-related database access
    Review database logs or audit logs for the alert module. Look for SQL queries containing suspicious patterns such as UNION SELECT, boolean-based injection, or time-based sleep functions within alert-related operations.
    Affected if Unexpected or malicious SQL patterns appear in database query logs related to the Alert feature

You are affected if your CMC or Guardian version is below 25.2.0 AND you have any alert configurations or alert functionality enabled in your environment.

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 parameterized queries (prepared statements) or proper input validation and sanititization for all input parameters in the Alert functionality to prevent SQL injection attacks.

Recommended fix Moderate confidence

25.2.0 or later for both Cmc and Guardian

  1. 1. Identify all instances running Cmc or Guardian versions prior to 25.2.0
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up the current configuration and database before proceeding
  4. 4. Obtain the version 25.2.0 or later from the official vendor distribution channel
  5. 5. Follow the vendor's standard upgrade procedure for Cmc and Guardian products
  6. 6. Verify the upgrade completed successfully by checking the product version
  7. 7. Confirm the SQL injection vulnerability is resolved by testing the Alert functionality with the input that previously triggered the issue
Caveat Check vendor release notes for any breaking changes between your current version and 25.2.0

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

Fix this in Cmc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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