CVE-2025-31349
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 · uneditedA 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 'UpdateSmtpSettings' 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-25919)
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 confidenceSQL injection vulnerability in TeleControl Server Basic's internal 'UpdateSmtpSettings' method allows authenticated remote attackers to bypass authorization controls, read from and write to the application's database, and execute code with NT AUTHORITY\NetworkService permissions via port 8000.
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< 3.1.2.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if TeleControl Server Basic is installedCheck the installed programs on the system for Siemens TeleControl Server Basic, or look for its installation directory. The application typically installs to C:\Program Files\Siemens\TeleControl Server Basic or similar paths.Affected if The application is present on the system and the version is below 3.1.2.2
-
Determine the installed versionLocate the version information in the application's about dialog, install directory, or Windows registry under HKLM\SOFTWARE\Siemens\TeleControl Server Basic. Compare the version number against the affected range of versions < 3.1.2.2.Affected if The installed version is any version prior to 3.1.2.2
-
Verify if port 8000 is exposedCheck if the application is listening on port 8000 by running 'netstat -an | findstr :8000' or using a port scanner. This is the port through which the vulnerable UpdateSmtpSettings method is accessible.Affected if Port 8000 is open and accessible from network locations where untrusted users could reach it
-
Confirm authentication configurationReview the application's user accounts and access control settings to determine if default credentials are in use or if weak authentication allows unauthorized users to access the UpdateSmtpSettings method.Affected if Anonymous or default credentials are enabled, or authentication can be bypassed for the UpdateSmtpSettings endpoint
A system is affected if TeleControl Server Basic version is below 3.1.2.2 and the UpdateSmtpSettings method on port 8000 is accessible to authenticated but untrusted users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.2.2
Upgrade to TeleControl Server Basic version V3.1.2.2 or later to remediate this vulnerability. As a defense-in-depth measure, implement parameterized queries or prepared statements for all database interactions.
TeleControl Server Basic V3.1.2.2 or later
- 1. Obtain TeleControl Server Basic version 3.1.2.2 or later from the official Siemens download portal or through your existing Siemens support channels.
- 2. Ensure you have a complete backup of the current TeleControl Server Basic installation and its database.
- 3. Verify network access requirements: the vulnerability requires access to port 8000, so ensure appropriate network segmentation or firewall rules are in place.
- 4. Stop the TeleControl Server Basic service before applying the upgrade.
- 5. Install version 3.1.2.2 or later following the standard Siemens upgrade procedures.
- 6. After installation, verify the application starts successfully and all services are running.
- 7. Confirm the UpdateSmtpSettings method is no longer vulnerable by reviewing release notes or patch documentation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-31349 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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