CVE-2025-40574
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 interact with the backupmanager service.
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 confidenceThe SCALANCE LPE9403 has improper permission assignment to critical resources, allowing a non-privileged local attacker to interact with the backupmanager service due to insufficient access controls on protected system resources.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SCALANCE LPE9403 device modelAccess the device web interface or CLI and retrieve the device model information from system status or device info pagesAffected if The device model is SCALANCE LPE9403 - all firmware versions are affected
-
Determine the installed firmware versionCheck the device firmware version through the web interface under System > Firmware or via CLI command 'show system info' or similarAffected if Any version below V4.0 HF0 indicates the device is running a vulnerable firmware version (all versions prior to V4.0 HF0 are affected)
-
Verify the backupmanager service is presentCheck for the presence of the backupmanager service on the device through CLI using 'ps' or 'show services' commands, or by examining /etc/init.d/ for backupmanager scriptsAffected if The backupmanager service exists on the device - the vulnerability allows non-privileged interaction with this service due to insufficient access controls
If the device is a SCALANCE LPE9403 running firmware versions prior to V4.0 HF0 and the backupmanager service is present, the environment is affected by CVE-2025-40574 due to improper permission assignment on the backupmanager service.
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 · scopedUpdate the device firmware to version V4.0 HF0 or later to remediate the permission misconfiguration.
V4.0 HF0
- 1. Identify the current firmware version of the SCALANCE LPE9403 device
- 2. Download the V4.0 HF0 firmware update from the official Siemens support portal (cert-portal.siemens.com)
- 3. Review the firmware upgrade instructions in the Siemens product documentation
- 4. Perform a backup of the current device configuration before upgrading
- 5. Upload and install the V4.0 HF0 firmware using the device's management interface
- 6. Verify the firmware upgrade was successful and the device is operating normally
- 7. Confirm the backupmanager service now has proper permission controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-40574 — 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-40574 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