dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-24499

HIGH · 7.2 CVSS v3.1 Published 2025-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 WAB762-1 (6GK5762-1AJ00-6AA0) (All versions < V3.0.0), SCALANCE WAM763-1 (6GK5763-1AL00-7DA0) (All versions < V3.0.0), SCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0) (All versions < V3.0.0), SCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0) (All versions < V3.0.0), SCALANCE WAM766-1 (6GK5766-1GE00-7DA0) (All versions < V3.0.0), SCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0) (All versions < V3.0.0), SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0) (All versions < V3.0.0), SCALANCE WUB762-1 (6GK5762-1AJ00-1AA0) (All versions < V3.0.0), SCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0) (All versions < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3AA0) (All versions < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3DA0) (All versions < V3.0.0), SCALANCE WUM763-1 (US) (6GK5763-1AL00-3AB0) (All versions < V3.0.0), SCALANCE WUM763-1 (US) (6GK5763-1AL00-3DB0) (All versions < V3.0.0), SCALANCE WUM766-1 (6GK5766-1GE00-3DA0) (All versions < V3.0.0), SCALANCE WUM766-1 (ME) (6GK5766-1GE00-3DC0) (All versions < V3.0.0), SCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0) (All versions < V3.0.0). Affected devices do not properly validate input while loading the configuration files. This could allow an authenticated remote attacker to execute arbitrary shell commands 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

This is a command injection vulnerability in Siemens SCALANCE WAB/WAM/WUB/WUM wireless access points and bridges. Affected devices fail to properly validate input when loading configuration files, allowing an authenticated remote attacker to inject and execute arbitrary shell commands on the device.

MitigationUpgrade all affected SCALANCE devices to firmware version V3.0.0 or later. If immediate upgrading is not feasible, limit device management interface access to authenticated, trusted personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 the SCALANCE device model
    Log into the device web interface or check the device label. Look for the exact model designation: WAB, WAM, WUB, or WUM.
    Affected if The model is one of WAB, WAM, WUB, or WUM (these are the affected product lines).
  2. Determine the installed firmware version
    In the device web interface, navigate to the System or Information section and locate the firmware version field. Alternatively, access the device CLI and run the command to display system information (for example, 'show version' or 'system info').
    Affected if The firmware version is earlier than V3.0.0 (versions prior to V3.0.0 are affected by this vulnerability).
  3. Verify if the web management interface is enabled
    In the device web interface, go to the System or Network settings and confirm whether the HTTP/HTTPS management interface is enabled. Check the access control settings to see which IP addresses or networks can reach the interface.
    Affected if The web management interface is exposed and accessible from untrusted networks (the command injection occurs when loading configuration files through this interface).
  4. Check if configuration file loading is accessible
    In the web interface, navigate to the Configuration or System > Configuration section. Look for options to load, import, or upload configuration files. Verify whether this feature is available to authenticated users.
    Affected if The configuration file upload/load feature is available to authenticated users (this is the attack vector for the command injection).

You are affected if you have a SCALANCE WAB, WAM, WUB, or WUM device running firmware version before V3.0.0 with the web management interface and configuration file loading feature accessible to authenticated users.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade all affected SCALANCE devices to firmware version V3.0.0 or later. If immediate upgrading is not feasible, limit device management interface access to authenticated, trusted personnel only.

Recommended fix High confidence

V3.0.0

  1. Identify the exact SCALANCE device model number (e.g., 6GK5762-1AJ00-6AA0) from the device label or web interface
  2. Check the current firmware version installed on the device through the web interface or command line
  3. Navigate to the Siemens industrial security website or Siemens support portal (siemens.com) and locate the SCALANCE WAB/WAM/WUB/WUM product page
  4. Download the firmware version V3.0.0 (or later if available) for the specific device model
  5. Access the device's web-based management interface using an administrator account
  6. Locate the firmware update or system maintenance section in the management interface
  7. Upload and apply the V3.0.0 firmware file following the on-screen instructions
  8. After the update completes, verify the new firmware version is reported as V3.0.0 or later
Caveat Review Siemens release notes for V3.0.0 to check for any configuration or feature changes that may require adjustments

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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