Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.1 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N · score source

EPSS

• CVE-2020-26249: 1.30% estimated exploitation activity in the next 30 days; percentile 70.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A RCE exploit has been discovered in the Red Discord Bot - Dashboard Webserver: this exploit allows Discord users with specially crafted Server names and Usernames/Nicknames to inject code into the webserver front-end code. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information. Patches This high severity exploit has been fixed on version 0.1.7a. Workarounds There are no workarounds, bot owners must upgrade their relevant packages (Dashboard module and Dashboard webserver) in order to patch this issue References - 99d88b8 - a6b9785 For more information If you have any questions or comments about this advisory: Open an issue in Cog-Creators/Red-Dashboard Over on the official Red Server or at the Third Party Server Toxic Layer

Published by the source

8 Dec 2020, 23:55 UTC

Last modified by the source

25 Oct 2024, 21:50 UTC

Source last checked

26 Oct 2026, 13:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hm45-mgqm-gjm4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-26249

Advisory: Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability
IDs: CVE-2020-26249, GHSA-hm45-mgqm-gjm4
Record: https://patchnext.com/advisories/cve-2020-26249 (revision 1, source checked 26 Oct 2026, 13:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: red-dashboard 0.1.7a0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI red-dashboard: affected <= 0.1.6a0; fixed in 0.1.7a0

## Suggested inspection (read-only)
- `python -m pip show red-dashboard`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on red-dashboard.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hm45-mgqm-gjm4 (GitHub-reviewed advisory GHSA-hm45-mgqm-gjm4 lists affected ranges: PyPI red-dashboard >=0 <=0.1.6a0)

Commands are suggestions: review each one before running it.