CVE-2021-33532
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 · uneditedIn Weidmueller Industrial WLAN devices in multiple versions an exploitable command injection vulnerability exists in the iw_webs functionality. A specially crafted diagnostic script file name can cause user input to be reflected in a subsequent iw_system call, resulting in remote control over the device. An attacker can send commands 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 confidenceCommand injection vulnerability in Weidmueller Industrial WLAN devices in the iw_webs functionality. User-supplied input from a diagnostic script file name is improperly reflected into an iw_system call without sanitization, allowing authenticated low-privilege users to execute arbitrary commands and gain full remote control of 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 data<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10<= 1.16.18<= 1.11.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device's web management interface or check the device label/ SNMP sysDescr to confirm it is a Weidmueller Industrial WLAN device (Ie Wl or Ie Wlt series)Affected if The device model matches one of: Ie Wl Bl Ap Cl Eu, Ie Wlt Bl Ap Cl Eu, Ie Wl Bl Ap Cl Us, Ie Wlt Bl Ap Cl Us, Ie Wl Vl Ap Br Cl Eu, Ie Wlt Vl Ap Br Cl Eu, Ie Wl Vl Ap Br Cl Us, Ie Wlt Vl Ap Br Cl Us
-
Check the firmware versionLog into the web interface and navigate to System > Firmware/Version or use SNMP to query the firmware version. Compare against the affected ranges.Affected if The firmware version is 1.16.18 or lower, OR 1.11.10 or lower (the device has two version tracks)
-
Verify iw_webs is accessibleConfirm the web management interface (iw_webs) is reachable on the device. Try accessing the diagnostic or system utilities section of the web UI.Affected if The web interface is accessible and includes diagnostic/script execution features
-
Check authentication statusDetermine if you can authenticate to the web interface with low-privilege credentials, or if default credentials are still in use.Affected if Low-privilege or default credentials provide access to the web management interface
If the device is a Weidmueller Industrial WLAN model from the affected list, runs firmware version 1.16.18 or lower (or 1.11.10 or lower), and the web interface is accessible with authenticated access, the environment is affected by CVE-2021-33532.
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 · scopedApply vendor-supplied firmware patches for affected versions; restrict network access to management interfaces and implement network segmentation for industrial devices until patching is possible.
Weidmueller Industrial WLAN firmware version > 1.16.18 (or > 1.11.10 depending on device series)
- Identify the exact Weidmueller Industrial WLAN device model from the affected product list (Ie Wl Bl Ap Cl Eu, Ie Wlt Bl Ap Cl Eu, Ie Wl Vl Ap Br Cl Eu, etc.)
- Access the device administrative interface or console
- Navigate to the firmware update section
- Check current firmware version (confirm it is <= 1.16.18 or <= 1.11.10)
- Obtain the latest firmware version from Weidmueller's official support website or contact Weidmueller technical support
- Upload and apply the updated firmware following Weidmueller's official upgrade procedure
- Verify the firmware update was successful
- Confirm the new firmware version is beyond 1.16.18 and 1.11.10
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33532 — 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-2021-33532 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