dbcve.org
Teamcenter VisualizationApplication · Siemens

CVE-2025-23397

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 14.3.0.13 / 2302.0021 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 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 confidence

Memory corruption vulnerability in Siemens Teamcenter Visualization and Tecnomatix Plant Simulation when parsing WRL (VRML) files. An attacker can achieve remote code execution by tricking a user into opening a specially crafted malicious WRL file, executing code in the context of the current process.

MitigationApply vendor patches: upgrade to Teamcenter Visualization V14.3.0.13, V2312.0009, V2406.0007, V2412.0002 or later; upgrade Tecnomatix Plant Simulation to V2302.0021, V2404.0010 or later. Until patched, do not open untrusted WRL files from unknown sources.

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
Teamcenter VisualizationApplication
Affected:>= 14.0.0, < 14.3.0.13>= 2312.0, < 2312.0009>= 2406.0, < 2406.0007>= 2412.0, < 2412.0002
Tecnomatix Plant SimulationApplication
Affected:>= 2302.0, < 2302.0021>= 2404.0, < 2404.0010

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Siemens product
    Determine whether Siemens Teamcenter Visualization or Tecnomatix Plant Simulation is installed. Check the program menu, installation directory, or software inventory for the product name.
    Affected if Neither product is installed - not affected. If either is present, proceed to version check.
  2. Check Teamcenter Visualization version
    Locate the Teamcenter Visualization installation and retrieve the version information (typically via Help > About, installation logs, or program executable properties).
    Affected if Version is 14.0.0 through 14.2.x, 2312.0 through 2312.0008, 2406.0 through 2406.0006, or 2412.0 through 2412.0001 - vulnerable.
  3. Check Tecnomatix Plant Simulation version
    Locate the Tecnomatix Plant Simulation installation and retrieve the version information (typically via Help > About, installation logs, or program executable properties).
    Affected if Version is 2302.0 through 2302.0020 or 2404.0 through 2404.0009 - vulnerable.
  4. Verify WRL file handling capability
    Determine whether the installation includes WRL/VRML file parsing functionality. Check for associated file handlers, import features, or visualization modules that process 3D WRL files.
    Affected if WRL parsing is available and enabled - the vulnerability can be triggered if a user opens a malicious WRL file.

You are affected if you have Teamcenter Visualization versions 14.0.0-14.2.x, 2312.0-2312.0008, 2406.0-2406.0006, or 2412.0-2412.0001; or Tecnomatix Plant Simulation versions 2302.0-2302.0020 or 2404.0-2404.0009, and the WRL parsing feature is present and can process untrusted files.

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 14.3.0.13 / 2302.0021 / 2312.0009 or later
Fixed in 14.3.0.132302.00212312.0009
Interim mitigation

Apply vendor patches: upgrade to Teamcenter Visualization V14.3.0.13, V2312.0009, V2406.0007, V2412.0002 or later; upgrade Tecnomatix Plant Simulation to V2302.0021, V2404.0010 or later. Until patched, do not open untrusted WRL files from unknown sources.

Recommended fix High confidence

Teamcenter Visualization: V14.3.0.13, V2312.0009, V2406.0007, V2412.0002 or later; Tecnomatix Plant Simulation: V2302.0021, V2404.0010 or later

  1. 1. Identify the currently installed Teamcenter Visualization or Tecnomatix Plant Simulation version
  2. 2. For Teamcenter Visualization: If running V14.x (>=14.0.0), upgrade to V14.3.0.13 or later
  3. 3. For Teamcenter Visualization: If running V2312.x, upgrade to V2312.0009 or later
  4. 4. For Teamcenter Visualization: If running V2406.x, upgrade to V2406.0007 or later
  5. 5. For Teamcenter Visualization: If running V2412.x, upgrade to V2412.0002 or later
  6. 6. For Tecnomatix Plant Simulation: If running V2302.x, upgrade to V2302.0021 or later
  7. 7. For Tecnomatix Plant Simulation: If running V2404.x, upgrade to V2404.0010 or later
  8. 8. Obtain the updated installer from Siemens Support Portal (cert-portal.siemens.com) or official channels
Caveat Review Siemens release notes for compatibility requirements; ensure third-party integrations support the target version before upgrading

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

Fix this in Teamcenter Visualization Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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