dbcve.org
Sinec NmsApplication · Siemens

CVE-2025-40755

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 4.0 or later.
See remediation →
94/100
Remediation priority · Urgent
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 vulnerability has been identified in SINEC NMS (All versions < V4.0 SP1). Affected applications are vulnerable to SQL injection through getTotalAndFilterCounts endpoint. An authenticated low privileged attacker could exploit to insert data and achieve privilege escalation. (ZDI-CAN-26570)

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 SINEC NMS in the getTotalAndFilterCounts endpoint allows authenticated low-privilege users to inject malicious SQL queries, potentially enabling data manipulation and privilege escalation to higher permissions.

MitigationUpgrade to SINEC NMS V4.0 SP1 or later. If immediate patching is not feasible, implement strict input validation and parameterized queries on the affected endpoint as a compensating control.

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
Sinec NmsApplication
Affected:< 4.0= 4.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 SINEC NMS installation version
    Locate the installed SINEC NMS version through the web interface (typically in Help > About or System > License information), or check the installation directory for version metadata files. On Windows, check the Windows Services list for 'SINEC NMS' service version, or review the installer logs.
    Affected if The installed version is lower than 4.0 or exactly version 4.0 (versions < 4.0 or = 4.0 are affected)
  2. Confirm web interface accessibility
    Verify that the SINEC NMS web interface is accessible by attempting to reach the application's URL (typically https://<hostname>/nms or similar). The vulnerable endpoint getTotalAndFilterCounts is part of the web application.
    Affected if The SINEC NMS web interface is reachable over the network and the application is operational
  3. Verify user authentication is enabled
    Check if SINEC NMS user authentication is configured and functional. Attempt to access the application without credentials or with low-privilege user credentials to confirm the authentication mechanism is active.
    Affected if Low-privilege authenticated users can access the application, as the vulnerability affects authenticated users with low permissions
  4. Inspect endpoint exposure
    Review web server or proxy logs for requests to the getTotalAndFilterCounts endpoint. This endpoint is typically found under the NMS web API path. Check if the application exposes REST API endpoints.
    Affected if The getTotalAndFilterCounts endpoint is accessible and responds to requests, indicating the vulnerable feature is enabled

A system is affected if SINEC NMS version is 4.0 or below, the web interface is accessible, and authenticated low-privilege users can access the getTotalAndFilterCounts endpoint.

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 4.0 or later
Fixed in 4.0
Interim mitigation

Upgrade to SINEC NMS V4.0 SP1 or later. If immediate patching is not feasible, implement strict input validation and parameterized queries on the affected endpoint as a compensating control.

Recommended fix High confidence

V4.0 SP1 (or later)

  1. 1. Identify the current SINEC NMS version by accessing the administration interface or checking system information.
  2. 2. Create a complete backup of the SINEC NMS configuration and database to ensure data can be restored if needed.
  3. 3. Review SINEC NMS upgrade documentation for V4.0 SP1 to understand prerequisites and migration requirements.
  4. 4. Schedule a maintenance window as upgrades may require downtime.
  5. 5. Upgrade SINEC NMS to version V4.0 SP1 or later following the official upgrade procedure.
  6. 6. After upgrade, verify the application is running correctly and test the getTotalAndFilterCounts endpoint functionality.
  7. 7. Confirm the SQL injection vulnerability is resolved by verifying the patch is applied.
Caveat Review release notes for any configuration or compatibility changes before upgrading

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

Fix this in Sinec Nms Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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