CVE-2025-32867
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 'CreateBackup' 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 confidenceTeleControl Server Basic versions before V3.1.2.2 contain an SQL injection vulnerability in the 'CreateBackup' method. An authenticated remote attacker who can reach port 8000 can exploit this to bypass authorization, read/write to the database, and execute code with NT AUTHORITY\NetworkService privileges.
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.
-
Confirm TeleControl Server Basic installationLocate the TeleControl Server Basic installation directory or check installed programs list to identify if the product is present on the systemAffected if The product is installed and running on the target system
-
Identify installed versionUse the product's built-in version information feature, check the About dialog, or inspect version metadata in the installation directory to determine the exact version numberAffected if The installed version is lower than 3.1.2.2 (e.g., 3.1.2.1, 3.1.0.x, or earlier)
-
Verify port 8000 accessibilityCheck if port 8000 is listening and accessible from network locations using tools such as netstat, telnet, or a port scanner from an external perspectiveAffected if Port 8000 is open and reachable from an untrusted network segment or from attacker-controlled systems
-
Confirm CreateBackup method exposureDetermine if the TeleControl Server Basic web service or API is accessible and the CreateBackup method is available as part of the exposed interfaceAffected if The web interface/API on port 8000 is accessible and the CreateBackup functionality is present without additional compensating controls
The environment is affected if TeleControl Server Basic is installed with a version lower than 3.1.2.2 and port 8000 is network-accessible to an attacker.
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 TeleControl Server Basic to version V3.1.2.2 or later to remediate the SQL injection vulnerability. Restrict network access to port 8000 as a compensating control until the upgrade is applied.
TeleControl Server Basic V3.1.2.2
- Obtain TeleControl Server Basic version 3.1.2.2 from the official Siemens support portal (cert-portal.siemens.com or Siemens Industry Online Support)
- Review the Siemens upgrade documentation for TeleControl Server Basic before proceeding
- Back up the current TeleControl Server Basic installation, including configuration files and the database
- Test the upgrade in a non-production/staging environment first
- Stop the TeleControl Server Basic service before performing the upgrade
- Install version 3.1.2.2 following Siemens standard upgrade procedures
- Verify the application starts correctly and the CreateBackup method functions properly
- Confirm the SQL injection vulnerability is remediated by testing or reviewing release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32867 — 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-32867 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