dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-45560

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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. In versions 8.2.6.4 and prior, wrap_line (app/modules/common/common.py:181-186) and highlight_word (app/modules/common/common.py:188-192) build raw HTML by string concatenation with no escaping. The frontend (app/static/js/script.js, log-viewer paths) uses .html(data) / .append(data) to inject the response body. Anyone able to write a line into a managed HAProxy/Nginx access log (i.e. anyone who can send an HTTP request to the public LB) can land an <svg/onload=…> payload that executes when a Roxy-WI admin opens the log viewer. At time of publication, there are no publicly available patches.

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 8.2.6.4 and prior contain a stored XSS vulnerability. The Python functions wrap_line and highlight_word in app/modules/common/common.py construct HTML strings by concatenating log data without any sanitization or escaping. When the frontend JavaScript renders this data using .html() or .append(), malicious payloads stored in HAProxy/Nginx access logs (such as <svg/onload=...>) execute in the admin's browser.

MitigationImplement HTML escaping in the Python backend before concatenating log data into HTML strings, or use text-content methods instead of .html()/.append() in the JavaScript frontend. Until a patch is available, restrict log viewer access to trusted admins and consider implementing Content-Security-Policy headers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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. Confirm Roxy-WI installation
    Locate the Roxy-WI installation directory. Common paths include /opt/roxy-wi, /var/www/roxy-wi, or the installation folder where roxy-wi was deployed. Look for the main application structure.
    Affected if Roxy-WI is not installed, this CVE does not apply.
  2. Check Roxy-WI version
    Find the version file or check the installed package version. In the Roxy-WI root directory, look for a version indicator (such as version.py, VERSION file, or the web interface About page). Compare the installed version to 8.2.6.4.
    Affected if Installed version is 8.2.6.4 or prior.
  3. Verify vulnerable Python functions exist
    Locate the file app/modules/common/common.py within the Roxy-WI installation. Open the file and search for the functions wrap_line and highlight_word. These functions should concatenate log data directly into HTML strings without sanitization.
    Affected if The functions wrap_line and highlight_word exist and perform raw string concatenation of log data.
  4. Confirm log viewer functionality is accessible
    Determine if the HAProxy/Nginx log viewer feature is enabled and accessible in Roxy-WI. This is typically found in the web interface under Log Viewer or similar section. Check if the feature is accessible to admin users.
    Affected if Log viewer functionality is enabled and accessible to users.
  5. Check frontend JavaScript rendering method
    Inspect the frontend templates or JavaScript files that render the log viewer. Look for usage of .html() or .append() jQuery methods that process log data returned from the backend.
    Affected if The frontend uses .html() or .append() to render log data, allowing script execution.

A user is affected if Roxy-WI version 8.2.6.4 or prior is installed, the vulnerable wrap_line/highlight_word functions exist in app/modules/common/common.py, and the log viewer feature is accessible with frontend code using .html() or .append() to render unsanitized log data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement HTML escaping in the Python backend before concatenating log data into HTML strings, or use text-content methods instead of .html()/.append() in the JavaScript frontend. Until a patch is available, restrict log viewer access to trusted admins and consider implementing Content-Security-Policy headers.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45560 — 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-45560 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