CVE-2025-25267
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 Tecnomatix Plant Simulation V2302 (All versions < V2302.0021), Tecnomatix Plant Simulation V2404 (All versions < V2404.0010). The affected application does not properly restrict the scope of files accessible to the simulation model. This could allow an unauthorized attacker to compromise the confidentiality of the system.
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 confidenceTecnomatix Plant Simulation versions prior to V2302.0021 and V2404.0010 fail to properly restrict the scope of files accessible to simulation models, potentially allowing unauthorized access to files outside the intended model scope and compromising system confidentiality.
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>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Locate Tecnomatix Plant Simulation installationCheck standard installation paths such as C:\Program Files\Siemens\Tecnomatix_Plant_Simulation or use Windows Programs and Features to find the installation directoryAffected if Installation directory not found means product may not be installed
-
Find version informationRight-click the main executable (usually PlantSimulation.exe) in the installation folder, select Properties, and view the File Version or Product Version field. Alternatively, check Add/Remove Programs for the installed version numberAffected if Unable to determine version means cannot verify vulnerability status
-
Compare against affected version rangesNote the full version number (e.g., 2302.0, 2302.0021, 2404.0, 2404.0010). Compare numerically: versions 2302.0 through 2302.0020 are vulnerable; versions 2404.0 through 2404.0009 are vulnerableAffected if Version is 2302.0 to 2302.0020 inclusive OR 2404.0 to 2404.0009 inclusive indicates the environment is affected by this improper file scope restriction vulnerability
A user is affected if Tecnomatix Plant Simulation is installed with a version number between 2302.0 and 2302.0020, or between 2404.0 and 2404.0009, since these versions fail to restrict file access to the intended model scope.
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 · scoped2302.00212404.0010
Upgrade Tecnomatix Plant Simulation to V2302.0021 or later, or V2404.0010 or later, as these versions contain the fix for improper file scope restriction.
Upgrade to Tecnomatix Plant Simulation V2302.0021 (for V2302 line) or V2404.0010 (for V2404 line)
- 1. Identify the currently installed version of Tecnomatix Plant Simulation by opening the application and navigating to Help > About, or checking the installation directory for version information.
- 2. If running version V2302.x with version < V2302.0021, or version V2404.x with version < V2404.0010, the system is vulnerable.
- 3. Back up any critical simulation models and project data before proceeding with the upgrade.
- 4. Obtain the fixed version (V2302.0021 or V2404.0010) from the official Siemens support portal or through your existing software distribution channel.
- 5. Uninstall the current vulnerable version, or use the upgrade/installation mechanism to install the fixed version over the existing installation.
- 6. After installation, verify the new version by checking Help > About to confirm V2302.0021 or V2404.0010 is installed.
- 7. Test critical simulation models to ensure functionality is maintained after the upgrade.
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-25267 — 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-25267 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