dbcve.org
Telecontrol Server BasicApplication · Siemens

CVE-2025-40765

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 TeleControl Server Basic V3.1 (All versions >= V3.1.2.2 < V3.1.2.3). The affected application contains an information disclosure vulnerability. This could allow an unauthenticated remote attacker to obtain password hashes of users and to login to and perform authenticated operations of the database service.

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

TeleControl Server Basic V3.1 contains an information disclosure vulnerability in versions >= V3.1.2.2 < V3.1.2.3 that allows unauthenticated remote attackers to obtain password hashes for all users in the system, enabling subsequent authenticated database operations.

MitigationUpgrade to TeleControl Server Basic V3.1.2.3 or later. If immediate patching is not possible, implement network segmentation and restrict database access to minimize exposure.

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
Telecontrol Server BasicApplication
Affected:= 3.1.2.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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 TeleControl Server Basic installation
    Locate the TeleControl Server Basic installation and determine its version number through the application UI, system information, or installed programs list
    Affected if The software is installed and the version is exactly 3.1.2.2
  2. Verify the exact version number
    Cross-reference the installed version against the affected range: V3.1.2.2 (versions >= V3.1.2.2 < V3.1.2.3). Confirm the precise version string matches 3.1.2.2
    Affected if Installed version is exactly 3.1.2.2 - this is the sole affected version in the specified range
  3. Assess network exposure
    Determine if the TeleControl Server Basic web interface or API endpoints are accessible from untrusted networks. Check firewall rules and network segmentation configurations
    Affected if The server is directly exposed to untrusted networks without proper access controls, allowing unauthenticated attackers to reach the vulnerable endpoint

You are affected only if TeleControl Server Basic version 3.1.2.2 is installed AND the server is network-accessible to unauthenticated attackers who could reach the endpoint that exposes user password hashes.

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 TeleControl Server Basic V3.1.2.3 or later. If immediate patching is not possible, implement network segmentation and restrict database access to minimize exposure.

Recommended fix High confidence

V3.1.2.3

  1. 1. Obtain TeleControl Server Basic version V3.1.2.3 from Siemens (cert-portal.siemens.com or official Siemens support channels)
  2. 2. Review release notes for V3.1.2.3 to confirm includes fix for CVE-2025-40765
  3. 3. Create full backup of current TeleControl Server Basic installation and database
  4. 4. Schedule maintenance window as upgrade may require service restart
  5. 5. Install TeleControl Server Basic V3.1.2.3 following Siemens installation documentation
  6. 6. Verify application starts successfully and all services are running
  7. 7. Test that authenticated operations work correctly post-upgrade
  8. 8. Confirm vulnerability is remediated by verifying unauthenticated access is no longer possible

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

Fix this in Telecontrol Server Basic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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