What is CVE-2020-26249?

CVE-2020-26249 is a medium-severity cross-site scripting (XSS) vulnerability in red-dashboard (pip), affecting versions <= 0.1.6a. It is fixed in 0.1.7a. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2020-26249?

CVE-2020-26249 has a CVSS score of 7.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of red-dashboard are affected by CVE-2020-26249?

red-dashboard (pip) versions <= 0.1.6a is affected.

Is there a fix for CVE-2020-26249?

Yes. CVE-2020-26249 is fixed in 0.1.7a. Upgrade to this version or later.

Is CVE-2020-26249 exploitable, and should I be worried?

Whether CVE-2020-26249 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-26249 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2020-26249?

Upgrade red-dashboard to 0.1.7a or later.

CVE-2020-26249 in red-dashboard

Q: How severe is CVE-2020-26249?

CVE-2020-26249 has a CVSS score of 7.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of red-dashboard are affected by CVE-2020-26249?

red-dashboard (pip) versions <= 0.1.6a is affected.

Q: Is there a fix for CVE-2020-26249?

Yes. CVE-2020-26249 is fixed in 0.1.7a. Upgrade to this version or later.

Q: Is CVE-2020-26249 exploitable, and should I be worried?

Whether CVE-2020-26249 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-26249 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-26249?

Upgrade red-dashboard to 0.1.7a or later.

Summary

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

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

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2020-26249 has a CVSS score of 7.7 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.7a); upgrading removes the vulnerable code path.

Affected versions

red-dashboard (<= 0.1.6a)

Security releases

red-dashboard → 0.1.7a (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This high severity exploit has been fixed on version 0.1.7a.

Frequently Asked Questions

What is CVE-2020-26249? CVE-2020-26249 is a medium-severity cross-site scripting (XSS) vulnerability in red-dashboard (pip), affecting versions <= 0.1.6a. It is fixed in 0.1.7a. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2020-26249? CVE-2020-26249 has a CVSS score of 7.7 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of red-dashboard are affected by CVE-2020-26249? red-dashboard (pip) versions <= 0.1.6a is affected.
Is there a fix for CVE-2020-26249? Yes. CVE-2020-26249 is fixed in 0.1.7a. Upgrade to this version or later.
Is CVE-2020-26249 exploitable, and should I be worried? Whether CVE-2020-26249 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-26249 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-26249? Upgrade red-dashboard to 0.1.7a or later.