CVE-2025-40572
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 SCALANCE LPE9403 (6GK5998-3GS00-2AC2) (All versions < V4.0 HF0). Affected devices do not properly assign permissions to critical ressources. This could allow a non-privileged local attacker to access sensitive information stored on the device.
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 confidenceSCALANCE LPE9403 firmware versions prior to V4.0 HF0 contain improper permission assignment to critical resources, allowing a non-privileged local attacker to access sensitive information stored on the device.
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 dataall versionsCVSS 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.
-
Identify the device modelAccess the device web interface or CLI and confirm the device model is SCALANCE LPE9403Affected if Device is a SCALANCE LPE9403
-
Check the firmware versionNavigate to the device firmware information page in the web interface or run the command to display firmware version (such as 'show version' or via the system info section)Affected if Firmware version is any version prior to V4.0 HF0 or the version cannot be verified as V4.0 HF0 or later
-
Verify firmware version stringCompare the displayed firmware version against the string 'V4.0 HF0' - look for the full version notation in the device diagnostics or about sectionAffected if Version string does not start with V4.0 HF0 or later (for example, V3.x, V2.x, V1.x)
-
Check for sensitive file accessAs a local user with non-administrative privileges, attempt to access device configuration files, logs, or system files that may contain credentials or sensitive dataAffected if Non-privileged local users can read files that should require elevated privileges
The device is affected if it is a SCALANCE LPE9403 running any firmware version prior to V4.0 HF0, as this version is the minimum required to remediate the improper permission assignment vulnerability.
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 · scopedUpgrade SCALANCE LPE9403 firmware to V4.0 HF0 or later to remediate the improper permission assignment vulnerability.
V4.0 HF0
- Identify the current firmware version of the SCALANCE LPE9403 device using the device's web interface or management console
- Obtain the fixed firmware version V4.0 HF0 or later from Siemens official support channels (cert-portal.siemens.com or Siemens Product Security Incident Response Team)
- Review Siemens firmware update documentation for the LPE9403 device before proceeding
- Upload and install the V4.0 HF0 firmware update following the manufacturer's recommended procedure
- After installation, verify the device is running V4.0 HF0 or later and confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40572 — 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-40572 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