CVE-2026-63586: Unauthenticated Remote Code Execution via Shell Injection in Web Management Interface
The web-based management interface uses a modified uhttpd server with CGI shell scripts. The HTTP Basic Authentication username, taken directly from the Authorization header without sanitization, is inserted into a shell command string executed via the system() function. By submitting a specially crafted username containing shell metacharacters, an unauthenticated attacker with network access to the device can escape the command context and execute arbitrary commands with root privileges.
Security readout for executives and security teams
Plain-English summary
A flaw in the device management interface may let any network-reachable attacker run operating-system commands as root without valid credentials. Successful exploitation could expose configuration and credentials, alter device behavior, or interrupt service. However, the supplied product records mark the listed versions “unaffected,” conflicting with the vulnerability description, so precise affected scope requires vendor confirmation.
Executive priority
Treat this as an immediate exposure-verification priority. Within the shortest operationally safe window, identify named devices and block untrusted management access. Escalate confirmed reachable instances for emergency containment and vendor-directed remediation. Because the supplied version status is contradictory, obtain authoritative clarification before declaring specific firmware affected or remediated.
Technical view
Unsanitized HTTP Basic Authentication usernames are inserted into a shell command executed through system(). Shell metacharacters can escape the intended command context, producing unauthenticated root-level command injection (CWE-78). CVSS 3.1 is 9.8 because exploitation is network-based, low-complexity, requires no privileges or user interaction, and may fully compromise confidentiality, integrity, and availability.
Likely exposure
Risk is highest where a listed device’s web management interface is reachable from untrusted, corporate, or compromised operational networks. The bundle names IE-SR-2TX-WL 1.52 and two 1.67 variants, but also marks them “unaffected.” Do not treat those version entries as confirmed exposure until reconciled with Weidmueller or CERT@VDE guidance.
Exploitation context
The bundle does not report active exploitation, and the CVE is not listed as KEV. The described attack requires only network access to the management interface and no valid credentials. Its low complexity and root-level outcome make exposed interfaces urgent to investigate, while current real-world exploitation status remains unconfirmed.
Researcher notes
The core trust-boundary failure is attacker-controlled Authorization-header data reaching a shell interpreter through system() without sanitization. Root execution follows from the CGI/web-server execution context described in the bundle. Product and firmware applicability remains ambiguous because all listed version records have defaultStatus “unaffected.” No patch version, workaround, proof of concept, or observed exploitation evidence is supplied.
Mitigation direction
Check the CERT@VDE advisory and Weidmueller guidance for confirmed affected versions, updates, or vendor mitigations.
Restrict web management access to authorized administration networks and trusted hosts.
Remove management interfaces from internet exposure and isolate affected devices from untrusted networks.
Disable remote web management where operationally safe until affected status and remediation are confirmed.
Monitor management-interface requests and device activity for anomalies or unexpected configuration changes.
Validation and detection
Inventory the named models, installed firmware versions, and management-interface network locations.
Verify whether each management interface is reachable from internet, user, vendor, wireless, or operational networks.
Compare inventory against the latest CERT@VDE and Weidmueller affected-version statements.
Review authentication and web-server logs for unusual Basic Authentication usernames or repeated malformed requests.
Check device integrity, configurations, accounts, and processes using approved defensive procedures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command
Improper Neutralization of Special Elements used in an OS Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.