dbcve.org
Simatic Pcs NeoApplication · Siemens

CVE-2025-40795

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 2.15.1.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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 stack-based buffer overflow vulnerability in the integrated UMC component. This could allow an unauthenticated remote attacker to execute arbitrary code or 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 · moderate confidence

A stack-based buffer overflow vulnerability exists in the User Management Component (UMC) integrated into SIMATIC PCS neo V4.1, V5.0, V6.0 (pre-SP1 Update 1), and standalone UMC versions prior to V2.15.1.3. This flaw can be exploited by an unauthenticated remote attacker to execute arbitrary code or cause a denial of service condition.

MitigationApply vendor patches: update SIMATIC PCS neo to V6.0 SP1 Update 1 or later, and UMC to V2.15.1.3 or later. Until patched, restrict network access to affected systems and monitor for indicators of compromise.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check if SIMATIC PCS neo is installed
    Use system inventory or software listing tools to identify if SIMATIC PCS neo is present on the system. Look for installation directories or registered software components related to PCS neo.
    Affected if SIMATIC PCS neo is installed and the version is 4.1, 5.0, or 6.0 prior to SP1 Update 1
  2. Determine the installed SIMATIC PCS neo version
    Access the installed version information through the product's about dialog, installation logs, or system registry entries if available. Compare the found version against the affected range.
    Affected if The installed version matches 4.1, 5.0, or any 6.0 version before SP1 Update 1
  3. Check for standalone User Management Component (UMC) installation
    Identify if the standalone UMC component is installed separately from SIMATIC PCS neo, using system inventory or installed programs list.
    Affected if Standalone UMC is installed with a version lower than 2.15.1.3
  4. Verify the UMC component version within SIMATIC PCS neo
    If SIMATIC PCS neo is installed, locate and inspect the UMC component version information within the product installation directory or through product-specific diagnostic tools.
    Affected if The UMC component version bundled with SIMATIC PCS neo is lower than 2.15.1.3

The environment is affected if SIMATIC PCS neo V4.1, V5.0, or V6.0 (pre-SP1 Update 1) is installed, or if standalone UMC version is below 2.15.1.3.

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

Apply vendor patches: update SIMATIC PCS neo to V6.0 SP1 Update 1 or later, and UMC to V2.15.1.3 or later. Until patched, restrict network access to affected systems and monitor for indicators of compromise.

Recommended fix High confidence

UMC: V2.15.1.3 or later; SIMATIC PCS neo V6.0: V6.0 SP1 Update 1 or later; Older versions (V4.1/V5.0): upgrade to V6.0 SP1 Update 1

  1. 1. Identify the User Management Component (UMC) version currently installed in the SIMATIC PCS neo environment.
  2. 2. For systems with UMC versions prior to V2.15.1.3, obtain and apply UMC version 2.15.1.3 or later from Siemens official download channels.
  3. 3. For SIMATIC PCS neo V6.0, ensure the installation is updated to V6.0 SP1 Update 1 or later.
  4. 4. For SIMATIC PCS neo V4.1 and V5.0 (all versions), consider upgrading to a newer supported version (V6.0 SP1 Update 1 or later) as these older major versions may have limited or no UMC patches available.
  5. 5. After applying the update, verify the UMC version reflects the patched release.
  6. 6. Test critical UMC workflows (authentication, user management) to confirm the system functions correctly post-update.
  7. 7. Document the update in the change management system and monitor for any unusual behavior.
Caveat Upgrading major PCS neo versions (e.g., from V4.1 or V5.0 to V6.0) may require compatibility checks with existing projects, dependencies, and integrations; always review Siemens migration documentation before upgrading.

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
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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