GHSA-hm45-mgqm-gjm4 is a high-severity (CVSS 7.7) Cross-site Scripting (XSS) vulnerability in red-dashboard. O3 Security confirms whether GHSA-hm45-mgqm-gjm4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Remote Code Execution (RCE) Exploit on Cross Site Scripting (XSS) Vulnerability
Real-World Exposure
red-dashboardReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | red-dashboard | all versions | 0.1.7a |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for red-dashboard. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update red-dashboard to 0.1.7a or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hm45-mgqm-gjm4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hm45-mgqm-gjm4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hm45-mgqm-gjm4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hm45-mgqm-gjm4 in your dependencies?
O3 detects GHSA-hm45-mgqm-gjm4 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.