dbcve.org
Telecontrol Server BasicApplication · Siemens

CVE-2025-32851

HIGH · 8.8 CVSS v3.1 Published 2025-04-16
Fix available
A fix is available. Upgrade to 3.1.2.2 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 TeleControl Server Basic (All versions < V3.1.2.2). The affected application is vulnerable to SQL injection through the internally used 'UnlockTcmSettings' method. This could allow an authenticated remote attacker to bypass authorization controls, to read from and write to the application's database and execute code with "NT AUTHORITY\NetworkService" permissions. A successful attack requires the attacker to be able to access port 8000 on a system where a vulnerable version of the affected application is executed on.

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 TeleControl Server Basic's UnlockTcmSettings method (versions < V3.1.2.2) allows authenticated remote attackers to bypass authorization, read/write the database, and execute code with NT AUTHORITY\NetworkService permissions via port 8000.

MitigationUpgrade to V3.1.2.2 or later; restrict network access to port 8000 to authorized users only until patched.

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
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 if TeleControl Server Basic is installed
    Check for the presence of TeleControl Server Basic in installed programs (Windows: Control Panel > Programs and Features, or check for installation directory typically under C:\Program Files\Siemens\ or similar)
    Affected if The software is installed on the system
  2. Check the installed version number
    Locate the version information in the program's installation directory, registry, or within the application itself. Common locations include the application's about screen, README files, or version.dll. Compare against the vulnerable range: versions before V3.1.2.2
    Affected if The installed version is earlier than V3.1.2.2
  3. Verify if port 8000 is listening and accessible
    Run 'netstat -an | findstr :8000' or use a port scanner to check if port 8000 is open and listening on the server's network interfaces
    Affected if Port 8000 is open and exposed to network access
  4. Confirm remote access exposure
    Check firewall rules and network configuration to determine if the server's port 8000 is reachable from external or untrusted networks. Review inbound firewall rules for applications allowing port 8000 connections
    Affected if Port 8000 is accessible from untrusted network segments or the internet
  5. Assess authentication configuration
    Review user accounts and authentication settings for TeleControl Server Basic to determine if default or weak credentials are in use, and verify which accounts have access to the UnlockTcmSettings method
    Affected if The UnlockTcmSettings method is accessible without proper authentication or with compromised credentials

A user is affected if TeleControl Server Basic versions before V3.1.2.2 are installed with port 8000 exposed to the network and the UnlockTcmSettings method is accessible without proper authorization controls.

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

Upgrade to V3.1.2.2 or later; restrict network access to port 8000 to authorized users only until patched.

Recommended fix High confidence

V3.1.2.2

  1. 1. Obtain the fixed version (V3.1.2.2) from the official Siemens download portal or your Siemens representative
  2. 2. Create a full backup of the TeleControl Server Basic installation and its database
  3. 3. Schedule a maintenance window as the upgrade may require service interruption
  4. 4. Stop the TeleControl Server Basic service before applying the update
  5. 5. Install version 3.1.2.2 following Siemens installation documentation
  6. 6. Verify the service starts successfully and confirm the application is operational
  7. 7. Test that the UnlockTcmSettings functionality works correctly after the upgrade
  8. 8. If possible, verify that the SQL injection vulnerability is no longer present through authorized penetration testing

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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