CVE-2025-23399
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 applications contain an out of bounds read past the end of an allocated structure 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 confidenceThis vulnerability is a memory corruption issue in Teamcenter Visualization and Tecnomatix Plant Simulation applications. The applications contain an out-of-bounds read vulnerability when parsing specially crafted WRL (VRML) files, which could allow an attacker to achieve code execution in the context of the current process.
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.
-
Check if Teamcenter Visualization is installedLook for Teamcenter Visualization installation directory, or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\TeamcenterVisualization for the InstallPath valueAffected if The product is installed on the system
-
Determine Teamcenter Visualization versionCheck the version information of the Visualization executable (typically TcVis.exe or related binaries) via file properties, or query the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\TeamcenterVisualization for the Version valueAffected if The installed version falls within >= 14.0.0 and < 14.3.0.13, OR >= 2312.0 and < 2312.0009, OR >= 2406.0 and < 2406.0007, OR >= 2412.0 and < 2412.0002
-
Check if Tecnomatix Plant Simulation is installedLook for Tecnomatix Plant Simulation installation directory (typically under C:\Program Files\Siemens\Tecnomatix_Plant_Simulation), or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\TecnomatixPlantSimulationAffected if The product is installed on the system
-
Determine Tecnomatix Plant Simulation versionCheck the version information of the Plant Simulation executable (typically PlantSimulation.exe) via file properties, or look for version info in the installation directory readme or about dialogAffected if The installed version falls within >= 2302.0 and < 2302.0021 OR >= 2404.0 and < 2404.0010
-
Verify WRL file handling capabilityConfirm that the installed application can open or import WRL (VRML) files - this is a standard visualization feature in both Teamcenter Visualization and Plant Simulation for 3D model viewingAffected if The application has the ability to parse WRL files (this is the default behavior for visualization workflows)
You are affected if either Teamcenter Visualization or Tecnomatix Plant Simulation is installed with a version matching the affected ranges and the application can process WRL files.
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 vendor-supplied patched versions: Teamcenter Visualization V14.3 to V14.3.0.13, V2312 to V2312.0009, V2406 to V2406.0007, V2412 to V2412.0002; Tecnomatix Plant Simulation V2302 to V2302.0021, V2404 to V2404.0010. Until patched, avoid opening untrusted WRL files from unknown sources.
Teamcenter Visualization: V14.3.0.13, V2312.0009, V2406.0007, or V2412.0002 (depending on branch); Tecnomatix Plant Simulation: V2302.0021 or V2404.0010 (depending on branch)
- 1. Identify the current installed version of Teamcenter Visualization or Tecnomatix Plant Simulation
- 2. Determine which product line and version branch is in use (V14.3, V2312, V2406, V2412, V2302, or V2404)
- 3. For Teamcenter Visualization V14.3: Upgrade to version 14.3.0.13 or later
- 4. For Teamcenter Visualization V2312: Upgrade to version 2312.0009 or later
- 5. For Teamcenter Visualization V2406: Upgrade to version 2406.0007 or later
- 6. For Teamcenter Visualization V2412: Upgrade to version 2412.0002 or later
- 7. For Tecnomatix Plant Simulation V2302: Upgrade to version 2302.0021 or later
- 8. For Tecnomatix Plant Simulation V2404: Upgrade to version 2404.0010 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-23399 — 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-23399 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