CVE-2022-31126
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 · uneditedRoxy-wi is an open source web interface for managing Haproxy, Nginx, Apache and Keepalived servers. A vulnerability in Roxy-wi allows a remote, unauthenticated attacker to code execution by sending a specially crafted HTTP request to /app/options.py file. This affects Roxy-wi versions before 6.1.1.0. Users are advised to upgrade. There are no known workarounds for this issue.
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 confidenceRoxy-wi versions before 6.1.1.0 contain an unauthenticated remote code execution vulnerability in the /app/options.py endpoint. Attackers can send specially crafted HTTP requests to execute arbitrary code on the target system without any credentials, leading to complete system compromise.
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< 6.1.1.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed Roxy-wi versionCheck the installed Roxy-wi version through the web interface (typically in About or System Info page) or by checking installed packages (e.g., rpm -qa roxy-wi, dpkg -l roxy-wi, or pip show roxy-wi depending on installation method)Affected if Version is lower than 6.1.1.0 or version cannot be determined but the product is confirmed as Roxy-wi
-
Verify the vulnerable endpoint existsLocate the /app/options.py file in the Roxy-wi installation directory - check common paths like /opt/roxy-wi/, /usr/share/roxy-wi/, or the application root directory where Roxy-wi is deployedAffected if The file /app/options.py exists in the installation directory (indicating the vulnerable code is present)
-
Confirm web interface is network accessibleDetermine if the Roxy-wi web interface is exposed to network access by reviewing firewall rules, reverse proxy configuration, or cloud security group settings that allow HTTP/HTTPS access to the Roxy-wi port (typically 8080 or 443)Affected if The web interface is reachable from untrusted networks (internet or other security zones without authentication controls)
-
Review access controls on the options endpointCheck if authentication is enforced for the /app/options.py endpoint by reviewing application configuration files, authentication middleware settings, or testing unauthenticated access to the endpointAffected if The /app/options.py endpoint can be accessed without valid authentication credentials
A system is affected if Roxy-wi version is confirmed below 6.1.1.0 AND the web interface is network-accessible, as the vulnerability allows unauthenticated remote code execution.
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.
dbcve · scoped6.1.1.0
Upgrade Roxy-wi to version 6.1.1.0 or later. No workarounds exist; immediate patching is required given the critical CVSS score and unauthenticated exploitation vector.
6.1.1.0
- Back up the current Roxy-WI installation and configuration
- Upgrade Roxy-WI to version 6.1.1.0
- Restart the Roxy-WI service
- Verify the upgrade was successful by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31126 — 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-2022-31126 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