CVE-2021-33533
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 iw_serverip parameter 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 where the iw_serverip parameter in the iw_webs web interface is not properly sanitized before being passed to iw_system calls, allowing authenticated low-privilege users to execute arbitrary system commands and gain 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 modelLocate the Weidmueller device and confirm the exact model number from the affected product list (Ie Wl Bl Ap Cl Eu, Ie Wlt Bl Ap Cl Eu, Ie Wl Vl Ap Br Cl Eu, Ie Wl Vl Ap Br Cl Us, or their variants)Affected if The model matches any of the affected products listed in the CVE
-
Check the firmware versionAccess the device web interface or use the command line interface to retrieve the firmware version. Typically found in the web GUI under System > Firmware/Version or via 'show version' CLI commandAffected if The installed firmware version is 1.16.18 or lower, or 1.11.10 or lower (any version <= 1.16.18 or <= 1.11.10 is affected)
-
Verify the iw_webs web interface is accessibleAttempt to access the device web management interface, typically on HTTP/HTTPS ports 80/443. The vulnerable endpoint involves the iw_webs serviceAffected if The web interface is reachable from the network where the attacker would be able to send the iw_serverip parameter requests
-
Confirm web management is enabled and remotely accessibleCheck the device network configuration settings to determine if remote web management (HTTP/HTTPS) is enabled and bound to routable IP addresses rather than only localhost or internal networksAffected if Remote web management is enabled and accessible from untrusted networks, allowing authenticated users to reach the iw_serverip parameter input point
A user is affected if they have a Weidmueller Industrial WLAN device from the affected product list running firmware version 1.16.18 or lower, or 1.11.10 or lower, with the web management interface (iw_webs) accessible to authenticated users.
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.
From vendor dataApply vendor-supplied firmware patches when available. As a compensating control, restrict access to the web management interface to trusted IP addresses only via network segmentation or firewall rules, and disable remote management interfaces if not required.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33533 — 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-33533 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