dbcve.org
Simatic Pcs NeoApplication · Siemens

CVE-2025-40797

HIGH · 7.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2.15.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 SIMATIC PCS neo V4.1 (All versions), SIMATIC PCS neo V5.0 (All versions), SIMATIC PCS neo V6.0 (All versions < V6.0 SP1 Update 1), User Management Component (UMC) (All versions < V2.15.1.3). Affected products contain a out-of-bounds read vulnerability in the integrated UMC component. This could allow an unauthenticated remote attacker to cause a denial of service condition.

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

An out-of-bounds read vulnerability exists in the User Management Component (UMC) of SIMATIC PCS neo. An unauthenticated remote attacker can exploit this vulnerability to cause a denial of service condition on affected systems.

MitigationUpgrade SIMATIC PCS neo to V6.0 SP1 Update 1 or later, and UMC to V2.15.1.3 or later. As an interim measure, restrict network access to the UMC interface and implement network segmentation to limit exposure.

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
Simatic Pcs NeoApplication
Affected:= 4.1= 5.0
User Management ComponentApplication
Affected:< 2.15.1.3

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check if SIMATIC PCS neo is installed
    Look for SIMATIC PCS neo installation directories or check Windows Programs and Features for 'SIMATIC PCS neo' entry. Check version displayed there.
    Affected if Version listed is 4.1 or 5.0 (the affected versions).
  2. Identify User Management Component (UMC) version
    Check the installed version of the Siemens User Management Component. This is typically found in the UMC admin console, or in Windows Programs and Features as 'Siemens User Management Component' or similar. Run the UMC diagnostic tool if available, or check version info on UMC service files.
    Affected if UMC version is lower than 2.15.1.3.
  3. Verify UMC service is running and exposed
    Check if the UMC service (typically listens on port 443 or 8443 for web-based UMC) is running and accessible from the network. Use netstat or similar tool to check for listening UMC-related services.
    Affected if UMC service is running and accessible on network ports (indicates potential exposure to unauthenticated attackers).
  4. Confirm UMC web interface is reachable
    Attempt to access the UMC login page via HTTP/HTTPS from a remote location or check access logs for external connection attempts to the UMC endpoint.
    Affected if UMC web interface is reachable from untrusted networks.

You are affected if SIMATIC PCS neo V4.1 or V5.0 is installed, OR if the User Management Component version is below 2.15.1.3 and the UMC service is network-accessible.

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 2.15.1.3 or later
Fixed in 2.15.1.3
Interim mitigation

Upgrade SIMATIC PCS neo to V6.0 SP1 Update 1 or later, and UMC to V2.15.1.3 or later. As an interim measure, restrict network access to the UMC interface and implement network segmentation to limit exposure.

Recommended fix High confidence

SIMATIC PCS neo V6.0 SP1 Update 1; UMC V2.15.1.3

  1. 1. Identify the currently installed version of SIMATIC PCS neo or User Management Component (UMC)
  2. 2. For SIMATIC PCS neo V6.0: Upgrade to V6.0 SP1 Update 1 or later
  3. 3. For User Management Component (UMC): Upgrade to V2.15.1.3 or later
  4. 4. For SIMATIC PCS neo V4.1 and V5.0: Contact Siemens technical support for available remediation options, as the advisory lists 'All versions' as affected without specifying a fixed release
  5. 5. After upgrading, verify the UMC component version matches the expected fixed version
  6. 6. Test that the UMC service starts correctly and normal authentication flows work
Caveat Upgrade to PCS neo V6.0 SP1 Update 1 may require prior installation of base V6.0 SP1; test in staging environment before production deployment

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

Fix this in Simatic Pcs Neo Scoped from the published advisory
  • Consultation8.0 h
  • Implementation6.0 h
  • Testing16.0 h
  • Review / QA8.0 h
38.0 hours of engineering $6,520
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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