dbcve.org
Ie Wl Bl Ap Cl Eu FirmwareOperating system · Weidmueller

CVE-2021-33530

HIGH · 8.8 CVSS v3.1 Published 2021-06-25
Fix available
A fix is available. Upgrade to after 1.16.18 or later.
See remediation →
94/100
Remediation priority · Urgent
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
In Weidmueller Industrial WLAN devices in multiple versions an exploitable command injection vulnerability exists in encrypted diagnostic script functionality of the devices. A specially crafted diagnostic script file can cause arbitrary busybox commands to be executed, resulting in remote control over the device. An attacker can send diagnostic while authenticated as a low privilege user to trigger this vulnerability.

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

Command injection vulnerability in Weidmueller Industrial WLAN devices allows authenticated low-privilege users to execute arbitrary busybox commands via specially crafted diagnostic script files. The vulnerability exists in the encrypted diagnostic script functionality, enabling remote control of the device.

MitigationApply vendor-supplied firmware updates addressing the command injection vulnerability. If no update available, consider network segmentation to limit exposure and monitor for unauthorized diagnostic script uploads.

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
Ie Wl Bl Ap Cl Eu FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wlt Bl Ap Cl Eu FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wl Bl Ap Cl Us FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wlt Bl Ap Cl Us FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wl Vl Ap Br Cl Eu FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wlt Vl Ap Br Cl Eu FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wl Vl Ap Br Cl Us FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10
Ie Wlt Vl Ap Br Cl Us FirmwareOperating system
Affected:<= 1.16.18<= 1.11.10

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

CVSS:3.1/AV:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device web interface or CLI and retrieve the exact model name (e.g., Ie Wl Bl Ap Cl Eu, Ie Wlt Bl Ap Cl Eu, etc.)
    Affected if The model matches any of the Weidmueller Ie Wl or Ie Wlt series devices (AP, CL, VL, Br variants for EU or US regions)
  2. Check the installed firmware version
    Log into the device admin interface and navigate to the firmware/version information section, or run the command 'cat /etc/version' or 'firmware-info' via CLI
    Affected if The firmware version is 1.16.18 or lower, OR version 1.11.10 or lower (two separate version branches exist)
  3. Verify diagnostic script functionality is enabled
    Check the device configuration for the encrypted diagnostic script feature - typically found under Diagnostics, Tools, or Advanced Settings in the web interface
    Affected if The encrypted diagnostic script upload/execution feature is present and enabled on the device
  4. Confirm user access to diagnostic scripts
    Check if any user account with low privileges (e.g., guest, viewer, or standard user) can access the diagnostic script upload functionality
    Affected if Authenticated users with low privileges can access and upload diagnostic script files

A user is affected if they have a Weidmueller Industrial WLAN device from the Ie Wl or Ie Wlt series running firmware version 1.16.18 or below (or 1.11.10 or below) AND the encrypted diagnostic script feature is enabled and accessible to low-privilege 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
Upgrade available Upgrade to a release after 1.16.18
Interim mitigation

Apply vendor-supplied firmware updates addressing the command injection vulnerability. If no update available, consider network segmentation to limit exposure and monitor for unauthorized diagnostic script uploads.

Recommended fix Moderate confidence

Upgrade to Weidmueller firmware version > 1.16.18 (e.g., latest 1.17.x or newer stable release) or > 1.11.10 (e.g., latest 1.11.x or newer stable release)

  1. Identify the specific Weidmueller Industrial WLAN device model in your environment
  2. Determine the current firmware version installed on the device
  3. Download the latest firmware version from Weidmueller's official support portal (weidmueller.com) or contact Weidmueller technical support
  4. Follow Weidmueller's official firmware upgrade procedure to update the device
  5. After upgrading, verify the device is functioning correctly and the vulnerability is resolved
  6. Ensure the diagnostic script functionality is tested to confirm the fix
Caveat Review Weidmueller release notes for any compatibility changes or configuration adjustments required after firmware upgrade

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

Fix this in Ie Wl Bl Ap Cl Eu Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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