dbcve.org
Telecontrol Server BasicApplication · Siemens

CVE-2025-32831

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 'UpdateProjectUserRights' 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 the UpdateProjectUserRights method of TeleControl Server Basic allows authenticated remote attackers to bypass authorization controls, read/write to the database, and execute code with NT AUTHORITY\NetworkService permissions.

MitigationUpgrade to version V3.1.2.2 or later. Additionally, restrict access to port 8000 to trusted IPs only until the patch is applied.

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 TeleControl Server Basic installation
    Locate the TeleControl Server Basic installation directory and locate the application executable or service. Check the program's version information typically found in the file properties or in a version file within the installation folder.
    Affected if The installed version is present and is lower than 3.1.2.2
  2. Determine the installed version
    Use the system's program information, the application's about dialog, or query the installed software registry entries (if on Windows) to retrieve the exact version number of TeleControl Server Basic.
    Affected if The version number returned is less than 3.1.2.2 (e.g., 3.1.0, 3.0.x, any version prior to 3.1.2.2)
  3. Verify the UpdateProjectUserRights method availability
    Examine the TeleControl Server Basic configuration or documentation to confirm whether the UpdateProjectUserRights method is exposed as part of the server's API or web service endpoints.
    Affected if The UpdateProjectUserRights method is enabled and accessible in the deployment
  4. Check network exposure on port 8000
    Use a network scanning tool or command (such as netstat or a port scanner) to determine if port 8000 is open and listening on the server hosting TeleControl Server Basic. Also verify firewall rules permitting access to this port.
    Affected if Port 8000 is exposed to untrusted or external network segments

You are affected if TeleControl Server Basic is installed with a version lower than 3.1.2.2 AND the UpdateProjectUserRights method is accessible, particularly if port 8000 is exposed to untrusted networks.

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 version V3.1.2.2 or later. Additionally, restrict access to port 8000 to trusted IPs only until the patch is applied.

Recommended fix High confidence

V3.1.2.2

  1. 1. Ensure you have a backup of the TeleControl Server Basic installation and its database before proceeding.
  2. 2. Download TeleControl Server Basic version 3.1.2.2 or later from the official Siemens support channels (e.g., Siemens Industry Online Support or cert-portal.siemens.com).
  3. 3. Verify the integrity of the downloaded package using checksums if provided by Siemens.
  4. 4. Stop the TeleControl Server Basic service to take the application offline.
  5. 5. Install version 3.1.2.2 following Siemens' standard installation procedures for this product.
  6. 6. Restart the TeleControl Server Basic service.
  7. 7. Verify that the application is functioning correctly and that the SQL injection vulnerability is no longer present.
  8. 8. Review system logs and database access logs to confirm no unauthorized access occurred during the upgrade process.

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

Fix this in Telecontrol Server Basic Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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