dbcve.org
Telecontrol Server BasicApplication · Siemens

CVE-2025-30003

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 'UpdateProjectConnections' 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. (ZDI-CAN-25910)

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

MitigationUpgrade to V3.1.2.2 or later; alternatively, restrict network access to port 8000 until patching is possible.

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
    Check for TeleControl Server Basic service on the system. Look for the installation directory, typically under C:\Program Files\Siemens\TeleControl Server Basic, or check Windows Services for a TeleControl-related service.
    Affected if The software is installed and the service exists on the system.
  2. Determine installed version
    Locate the version information in the installation directory. Check for a version file, or right-click the main executable (typically TCServerBasic.exe or similar) and view Properties > Details to find the File Version. Alternatively, check the Windows Programs and Features list for the installed version.
    Affected if The installed version is lower than V3.1.2.2 (for example, V3.1.2.1, V3.1.2.0, or any version starting with 3.1.x below 3.1.2.2).
  3. Verify port 8000 accessibility
    Run 'netstat -an | findstr :8000' or use a port scanner to check if port 8000 is listening on the network interfaces. Confirm if the service is bound to 0.0.0.0:8000 or a specific network-adapter IP.
    Affected if Port 8000 is listening and accessible from network interfaces (not localhost-only).
  4. Check UpdateProjectConnections method exposure
    If port 8000 is open, verify the TeleControl Server Basic web service or API is reachable. Attempt a simple request to the UpdateProjectConnections endpoint, or check if the WSDL/API documentation is accessible on port 8000.
    Affected if The web service/API on port 8000 responds to requests, indicating the vulnerable method is potentially exposed.

The environment is affected if TeleControl Server Basic is installed with a version lower than V3.1.2.2 and port 8000 is accessible on the network, allowing external access to the UpdateProjectConnections method.

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; alternatively, restrict network access to port 8000 until patching is possible.

Recommended fix High confidence

TeleControl Server Basic V3.1.2.2 or later

  1. 1. Identify the current version of TeleControl Server Basic installed on the system
  2. 2. Obtain TeleControl Server Basic V3.1.2.2 or later from the official Siemens support portal (cert-portal.siemens.com)
  3. 3. Follow Siemens standard upgrade procedures for TeleControl Server Basic, ensuring backup of current configuration
  4. 4. After upgrade, verify the version is V3.1.2.2 or higher
  5. 5. Ensure port 8000 access is restricted to authorized personnel only as a defense-in-depth measure

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

Fix this in Telecontrol Server Basic Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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