# CVE-2022-31137: Unauthenticated Remote Code Execution in Roxy-WI

> Unauthenticated attackers can execute arbitrary system commands on Roxy-WI servers due to improper input handling in the options module.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-53r2-mq99-f532

## What is CVE-2022-31137?

CVE-2022-31137 is a critical command injection vulnerability in hap-wi roxy-wi, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2022-31137?

It affects 1 product.


Products: Roxy-Wi Roxy-Wi.

## How do I fix CVE-2022-31137?

No fix has been published for CVE-2022-31137 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-31137 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31137 exists.

Public exploit code:

- Roxy-WI Prior to 6.1.1.0 Unauthenticated Command Injection RCE (metasploit)
- Roxy-WI < 6.1.1.0 - Remote Code Execution (nuclei): http/cves/2022/CVE-2022-31137.yaml

## Other vulnerabilities in hap-wi roxy-wi

- [CVE-2022-31161](https://insights.sbomify.com/CVE-2022-31161/): Roxy-WI Vulnerable to Unauthenticated Remote Code Execution via ssl_cert Upload (critical 10.0)
- [CVE-2022-31125](https://insights.sbomify.com/CVE-2022-31125/): Authentication Bypass in Roxy-wi (critical 10.0)
- [CVE-2022-31126](https://insights.sbomify.com/CVE-2022-31126/): Unauthenticated Remote Code Execution in Roxy-wi (critical 10.0)
- [CVE-2021-38167](https://insights.sbomify.com/CVE-2021-38167/): SQL injection in n/a (critical 9.8)
- [CVE-2026-33076](https://insights.sbomify.com/CVE-2026-33076/): Roxy-WI vulnerable to path traversal and arbitrary file writing (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31137 and fix it if it is affected.

What it is: CVE-2022-31137 is a critical command injection vulnerability in hap-wi roxy-wi, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-31137 exists.

Affected product: hap-wi roxy-wi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31137/ (Markdown: https://insights.sbomify.com/CVE-2022-31137/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31137
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31137
- OSV: https://osv.dev/vulnerability/CVE-2022-31137

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31137/
Summaries are generated and may contain mistakes; the official description above is the record.