CVE-2025-23400
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 Teamcenter Visualization V14.3 (All versions < V14.3.0.13), Teamcenter Visualization V2312 (All versions < V2312.0009), Teamcenter Visualization V2406 (All versions < V2406.0007), Teamcenter Visualization V2412 (All versions < V2412.0002), Tecnomatix Plant Simulation V2302 (All versions < V2302.0021), Tecnomatix Plant Simulation V2404 (All versions < V2404.0010). The affected application is vulnerable to memory corruption while parsing specially crafted WRL files. This could allow an attacker to execute code in the context of the current process.
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 confidenceMemory corruption vulnerability in Teamcenter Visualization and Tecnomatix Plant Simulation when parsing specially crafted WRL (VRML) files. The vulnerability allows attackers to achieve code execution in the context of the current process due to insufficient bounds checking during WRL file parsing.
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>= 14.0.0, < 14.3.0.13>= 2312.0, < 2312.0009>= 2406.0, < 2406.0007>= 2412.0, < 2412.0002>= 2302.0, < 2302.0021>= 2404.0, < 2404.0010CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Teamcenter Visualization installationLocate the Teamcenter Visualization installation directory (commonly under C:\Program Files\Siemens\TeamcenterVisualization or /usr/siemens/teamcenter_visualization). Look for executable files such as Visualization.exe or related binaries.Affected if Teamcenter Visualization is installed and the version falls within any of the affected ranges (>=14.0.0 to <14.3.0.13, >=2312.0 to <2312.0009, >=2406.0 to <2406.0007, or >=2412.0 to <2412.0002)
-
Confirm Tecnomatix Plant Simulation installationLocate the Tecnomatix Plant Simulation installation directory (commonly under C:\Program Files\Siemens\Tecnomatix_Plant_Simulation or similar). Look for the main executable (PlantSimulation.exe or similar).Affected if Tecnomatix Plant Simulation is installed and the version falls within any of the affected ranges (>=2302.0 to <2302.0021 or >=2404.0 to <2404.0010)
-
Determine Teamcenter Visualization versionRight-click on the main executable (e.g., Visualization.exe), select Properties, and view the Version tab. Alternatively, check the version in the Siemens Licensing Tool or in the product's About dialog accessible from the Help menu.Affected if The installed version number is less than the fixed versions: 14.3.0.13, 2312.0009, 2406.0007, or 2412.0002 depending on the release line
-
Determine Tecnomatix Plant Simulation versionOpen Tecnomatix Plant Simulation, go to Help > About, or right-click the main executable and view the Version tab. The version is typically displayed as a four-digit release (e.g., 2302.0, 2404.0).Affected if The installed version number is less than the fixed versions: 2302.0021 or 2404.0010 depending on the release line
-
Check for WRL file handling capabilitySearch the installation directory for WRL-related files, parsers, or converters. Look for file associations or import/export functionality that handles .wrl files. In the product UI, check File > Open or Import for .wrl file type support.Affected if The product has the capability to import, open, or parse WRL (VRML) files, which is required for the vulnerability to be exploitable
The environment is affected if either Teamcenter Visualization or Tecnomatix Plant Simulation is installed with a version falling within the affected ranges and WRL file handling functionality is present.
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 · scoped14.3.0.132302.00212312.0009
Update affected products to the specified minimum versions: Teamcenter Visualization V14.3.0.13, V2312.0009, V2406.0007, V2412.0002; Tecnomatix Plant Simulation V2302.0021, V2404.0010. Until patches are applied, disable handling of untrusted WRL files and restrict user privileges where possible.
Upgrade to the minimum fixed version for your product line: Teamcenter Visualization V14.3.0.13, V2312.0009, V2406.0007, or V2412.0002; Tecnomatix Plant Simulation V2302.0021 or V2404.0010
- 1. Identify the exact version of Teamcenter Visualization or Tecnomatix Plant Simulation currently installed
- 2. For Teamcenter Visualization: If running version 14.0.0 to <14.3.0.13, upgrade to V14.3.0.13 or later
- 3. For Teamcenter Visualization: If running version 2312.0 to <2312.0009, upgrade to V2312.0009 or later
- 4. For Teamcenter Visualization: If running version 2406.0 to <2406.0007, upgrade to V2406.0007 or later
- 5. For Teamcenter Visualization: If running version 2412.0 to <2412.0002, upgrade to V2412.0002 or later
- 6. For Tecnomatix Plant Simulation: If running version 2302.0 to <2302.0021, upgrade to V2302.0021 or later
- 7. For Tecnomatix Plant Simulation: If running version 2404.0 to <2404.0010, upgrade to V2404.0010 or later
- 8. Verify the upgrade was successful by checking the application version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23400 — 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-23400 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