Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2022-31137 is a critical-severity OS Command Injection (CWE-78) vulnerability in Roxy-Wi Roxy-Wi. Its CVSS base score is 10.0 (Critical).
Operationally, ranked in the top 0.2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Roxy-WI is a web interface for managing HAProxy, Nginx, Apache, and Keepalived servers. Versions prior to 6.1.1.0 contain a remote code execution vulnerability caused by missing input validation in the subprocess_execute function within /app/options.py, which directly passes user-supplied data to system commands and corresponds to CWE-78.
Unauthenticated attackers with network access can exploit the flaw remotely to execute arbitrary operating-system commands. The CVSS 3.1 score of 10.0 reflects the absence of required authentication, privileges, or user interaction combined with full confidentiality, integrity, and availability impact under a changed scope.
Public references include multiple PacketStorm exploit files demonstrating remote command execution against versions 6.1.0.0 and earlier, along with the corrective commit that addresses the issue. The project advisory states that users should upgrade to 6.1.1.0 or later, as no workarounds are known. The associated EPSS score remains consistently high, with a current value of 0.9397 and a peak of 0.9498.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-52765
Vulnerability Data
Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. Versions prior to 6.1.1.0 are subject to a remote code execution vulnerability. System commands can be run remotely via the subprocess_execute function without processing the inputs received…
more
from the user in the /app/options.py file. Attackers need not be authenticated to exploit this vulnerability. Users are advised to upgrade. There are no known workarounds for this vulnerability.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation of untrusted inputs before they are passed to subprocess_execute, blocking the CWE-78 command injection.
Enforces that only authenticated and authorized users may invoke any functionality, eliminating the unauthenticated remote execution path.
Requires prompt application of the vendor patch (upgrade to 6.1.1.0) that removes the vulnerable code path.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.