CVE-2025-32846
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 'LockGeneralSettings' 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 confidenceSQL injection vulnerability in TeleControl Server Basic's LockGeneralSettings method allows authenticated remote attackers to bypass authorization and read/write to the database, potentially executing code with NT AUTHORITY\NetworkService privileges 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 TeleControl Server Basic installation and versionLocate the TeleControl Server Basic installation directory and check the version file or executable properties. Common paths include C:\Program Files\Siemens\TeleControl Server Basic\ or check the Windows installed programs list.Affected if The installed version is lower than 3.1.2.2 or the version cannot be determined (assumed vulnerable).
-
Verify port 8000 is listeningRun 'netstat -an | findstr :8000' or 'Get-NetTCPConnection -LocalPort 8000' to check if the TeleControl Server Basic service is listening on port 8000.Affected if Port 8000 is in LISTENING state and accessible from network locations.
-
Check network exposure of port 8000Review firewall rules using 'netsh advfirewall firewall show rule name=all' or check network perimeter configurations to determine if port 8000 is exposed to untrusted networks.Affected if Port 8000 is accessible from outside the trusted network or from non-localhost addresses.
-
Confirm authentication is required for the LockGeneralSettings methodReview application configuration files or documentation to verify whether authentication is enforced for the LockGeneralSettings API method.Affected if Authentication is not enforced or can be bypassed for this method (vulnerability requires valid authentication credentials).
If TeleControl Server Basic version is below 3.1.2.2 AND port 8000 is exposed on the network, the environment is affected by this authenticated SQL injection vulnerability.
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 version V3.1.2.2 or later; implement network segmentation to restrict port 8000 access to trusted sources only until patch is applied.
TeleControl Server Basic V3.1.2.2
- Obtain TeleControl Server Basic version 3.1.2.2 from the official Siemens download portal or through your Siemens support channel
- Create a complete backup of the current TeleControl Server Basic installation and database
- Stop the TeleControl Server Basic service to prevent active connections during the upgrade
- Install version 3.1.2.2 of TeleControl Server Basic following the standard upgrade procedure provided in Siemens documentation
- Start the TeleControl Server Basic service and verify it runs correctly
- Test the LockGeneralSettings method to confirm the SQL injection vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32846 — 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-32846 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