dbcve.org
Scalance Lpe9403 FirmwareOperating system · Siemens

CVE-2025-27392

HIGH · 7.2 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 4.0 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 SCALANCE LPE9403 (6GK5998-3GS00-2AC2) (All versions < V4.0). Affected devices do not properly sanitize user input when creating new VXLAN configurations. This could allow an authenticated highly-privileged remote attacker to execute arbitrary code 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 confidence

The SCALANCE LPE9403 devices (6GK5998-3GS00-2AC2) running firmware versions prior to V4.0 contain an input sanitization flaw in the VXLAN configuration interface. Insufficient validation of user-supplied input during VXLAN profile creation permits an authenticated attacker with high privileges to inject and execute arbitrary code on the device.

MitigationUpgrade SCALANCE LPE9403 firmware to V4.0 or later to obtain the vendor patch. If immediate upgrade is not feasible, restrict administrative access to trusted personnel only and monitor for suspicious VXLAN configuration activity.

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
Scalance Lpe9403 FirmwareOperating system
Affected:< 4.0

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify device model
    Access the device web interface or CLI and retrieve the hardware model identifier (should be 6GK5998-3GS00-2AC2 or SCALANCE LPE9403)
    Affected if Device is not a SCALANCE LPE9403 unit
  2. Check firmware version
    In the device web interface, navigate to System > Information or use CLI command to display firmware version (commonly 'show version' or via web UI status page)
    Affected if Firmware version is below V4.0 (e.g., V3.x, V2.x)
  3. Verify VXLAN feature status
    In the device web interface, navigate to VXLAN configuration section or use CLI to list VXLAN profiles (commonly 'show vxlan' or via Layer 2 > VXLAN settings)
    Affected if VXLAN feature is actively configured with one or more profiles
  4. Confirm administrative access exists
    Review user accounts in System > User Management or use CLI to list accounts with high privileges (administrator-level access)
    Affected if High-privilege authenticated accounts exist on the device

The device is affected if it is a SCALANCE LPE9403 running firmware prior to V4.0 and has VXLAN profiles configured with high-privilege administrative access enabled.

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

Upgrade SCALANCE LPE9403 firmware to V4.0 or later to obtain the vendor patch. If immediate upgrade is not feasible, restrict administrative access to trusted personnel only and monitor for suspicious VXLAN configuration activity.

Recommended fix High confidence

V4.0

  1. Identify the current firmware version of the SCALANCE LPE9403 device by accessing the device web interface or using the management console
  2. Navigate to the official Siemens cert-portal.siemens.com and locate the SCALANCE LPE9403 firmware V4.0 or later
  3. Download the V4.0 firmware file from the Siemens support portal
  4. Access the device management interface and navigate to the firmware update section
  5. Upload and install the V4.0 firmware following the Siemens firmware upgrade procedure
  6. After reboot, verify the device is running V4.0 or later and confirm the VXLAN configuration functionality works correctly
Caveat Review Siemens release notes for V4.0 to check for any configuration changes or feature modifications that may require adjustment

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

Fix this in Scalance Lpe9403 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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