dbcve.org
Telecontrol Server BasicApplication · Siemens

CVE-2025-32837

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 'GetActiveConnectionVariables' 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 GetActiveConnectionVariables method allows authenticated remote attackers to bypass authorization, read/write to the database, and execute code with NetworkService permissions. All versions prior to V3.1.2.2 are affected.

MitigationUpgrade to version V3.1.2.2 or later to patch the SQL injection vulnerability. As a compensating control, restrict access to port 8000 to trusted IPs only until the upgrade 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 or check the program's version information through the Windows Programs and Features, installation logs, or product's built-in version check (if available)
    Affected if The product is installed but the version cannot be determined or is shown as below V3.1.2.2
  2. Verify the installed version against vulnerable range
    Compare the installed version number to the affected version range: any version prior to V3.1.2.2 is vulnerable. Look for version displayed in the product UI, about dialog, or version file within the installation directory
    Affected if Installed version is lower than 3.1.2.2 (e.g., 3.1.2.1, 3.1.0.0, 2.x.x.x, etc.)
  3. Confirm network exposure of the service
    Determine if the TeleControl Server Basic service is listening on port 8000 (the default management port). Use netstat or port scanning tools to check if port 8000 is open and accessible from network
    Affected if Port 8000 is open and accessible from untrusted network segments
  4. Check if remote authentication is enabled
    Review the TeleControl Server Basic configuration to determine if remote authentication is required for the GetActiveConnectionVariables API method. Check authentication settings in the product's configuration files or management interface
    Affected if Remote authentication is configured and the service is network-accessible (the SQL injection requires authentication but attacker may use valid credentials to exploit)

You are affected if TeleControl Server Basic is installed with any version prior to V3.1.2.2 and the service is network-accessible with remote authentication enabled.

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 to patch the SQL injection vulnerability. As a compensating control, restrict access to port 8000 to trusted IPs only until the upgrade is applied.

Recommended fix High confidence

TeleControl Server Basic V3.1.2.2

  1. Verify the current installed version of TeleControl Server Basic
  2. Download TeleControl Server Basic version 3.1.2.2 from the official Siemens support portal (cert-portal.siemens.com)
  3. Backup the current application configuration and database
  4. Stop the TeleControl Server Basic service
  5. Install version 3.1.2.2 following the Siemens installation documentation
  6. Restart the TeleControl Server Basic service
  7. Verify the application is running correctly and the GetActiveConnectionVariables method is functioning as expected
Caveat Review Siemens release notes for V3.1.2.2 for any configuration or compatibility changes before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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