How severe is CVE-2022-31137?

CVE-2022-31137 has a CVSS score of 10/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31137?

Affected package information for CVE-2022-31137 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-31137?

No fixed version has been published for CVE-2022-31137 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-31137 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2022-31137, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-31137?

CVE-2022-31137 has an EPSS (Exploit Prediction Scoring System) score of 94.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2022-31137?

A Nuclei detection template exists for CVE-2022-31137, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-31137 published, and has it been updated?

CVE-2022-31137 was published on July 8, 2022 and was last updated on April 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2022-31137

CRITICAL

Unauthenticated Remote Code Execution in Roxy-WI

Also known asGHSA-53r2-mq99-f532

Published

Jul 8, 2022

Updated

Apr 2, 2026

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

94.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepa…

github.comMetasploitJul 2022

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepa…

packetstormsecurity.comNVDNov 2022

Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepa…

microsoft.comAPIDec 2022

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-31137 in your stack?

O3 detects CVE-2022-31137 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works