dbcve.org
Roxy WiApplication

CVE-2026-33078

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 8.2.6.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 · unedited
Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. Versions prior to 8.2.6.4 have a SQL injection vulnerability in the haproxy_section_save function in app/routes/config/routes.py. The server_ip parameter, sourced from the URL path, is passed unsanitized through multiple function calls and ultimately interpolated into a SQL query string using Python string formatting, allowing attackers to execute arbitrary SQL commands. Version 8.2.6.4 fixes the 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 confidence

Roxy-WI versions before 8.2.6.4 contain a SQL injection vulnerability in the haproxy_section_save function within app/routes/config/routes.py. The server_ip parameter, extracted from the URL path, is passed unsanitized through multiple function calls and directly interpolated into a SQL query string using Python string formatting, allowing unauthenticated attackers to execute arbitrary SQL commands.

MitigationUpgrade Roxy-WI to version 8.2.6.4 or later, which implements proper input sanitization and parameterized queries to address the SQL injection vulnerability.

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
Roxy WiApplication
Affected:< 8.2.6.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate Roxy-WI installation and identify version
    Find the Roxy-WI installation directory, then look for a version file, changelog, or version identifier within the installation. Common locations include the root directory or configuration files.
    Affected if The installed version is found to be lower than 8.2.6.4
  2. Inspect the vulnerable source file
    Navigate to app/routes/config/routes.py within the Roxy-WI installation and examine the haproxy_section_save function for the presence of SQL query construction using Python string formatting with the server_ip parameter.
    Affected if The file contains the haproxy_section_save function with direct string interpolation of server_ip into SQL queries
  3. Verify the function is accessible
    Determine whether the haproxy_section_save endpoint is exposed without authentication by checking route definitions and any access control configurations.
    Affected if The endpoint is accessible without authentication (as noted in the CVE, it is described as allowing unauthenticated attackers)

You are affected if your Roxy-WI version is below 8.2.6.4 and the vulnerable code in app/routes/config/routes.py is present with the haproxy_section_save function using unsanitized server_ip parameter in SQL queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 8.2.6.4 or later
Fixed in 8.2.6.4
Vendor patch github.com →
Interim mitigation

Upgrade Roxy-WI to version 8.2.6.4 or later, which implements proper input sanitization and parameterized queries to address the SQL injection vulnerability.

Recommended fix High confidence

8.2.6.4

  1. Identify the current installed version of Roxy-WI
  2. Review release notes or changelog for version 8.2.6.4 to understand any specific upgrade requirements
  3. Follow the standard upgrade procedure for Roxy-WI (refer to official documentation for your deployment method)
  4. Upgrade Roxy-WI to version 8.2.6.4
  5. Verify the upgrade was successful by checking the installed version
  6. Test that the haproxy_section_save function works correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Roxy Wi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,590
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33078 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33078 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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