Remote Code Execution in Red Discord Bot
CVE-2020-15140GHSA-55j9-849x-26h4
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (red-discordbot 3.3.11), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI red-discordbot
- Affected
- < 3.3.11
- Fixed in
- 3.3.11
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-55j9-849x-26h4 lists affected ranges: PyPI red-discordbot >=0 <3.3.11 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-55j9-849x-26h4 lists affected ranges: PyPI red-discordbot >=0 <3.3.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N · score source
- EPSS
- CVE-2020-15140: 1.16% estimated exploitation activity in the next 30 days; percentile 67.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact A RCE exploit has been discovered in the Trivia module: this exploit allows Discord users with specifically crafted usernames to inject code into the Trivia module's leaderboard command. By abusing this exploit, it's possible to perform destructive actions and/or access sensitive information. Patches This critical exploit has been fixed on version 3.3.11. Workarounds Unloading the Trivia module with unload trivia can render this exploit not accessible. We still highly recommend updating to 3.3.11 to completely patch this issue. References https://github.com/Cog-Creators/Red-DiscordBot/pull/4175 For more information If you have any questions or comments about this advisory: Open an issue in Cog-Creators/Red-DiscordBot Over on our Discord server
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-55j9-849x-26h4
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-55j9-849x-26h4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2020-15140 Advisory: Remote Code Execution in Red Discord Bot IDs: CVE-2020-15140, GHSA-55j9-849x-26h4 Record: https://patchnext.com/advisories/cve-2020-15140 (revision 3, 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.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: red-discordbot 3.3.11. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI red-discordbot: affected < 3.3.11; fixed in 3.3.11 ## Suggested inspection (read-only) - `python -m pip show red-discordbot`: 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-discordbot. - 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://osv.dev/vulnerability/GHSA-55j9-849x-26h4 (OSV record GHSA-55j9-849x-26h4 lists affected ranges: PyPI red-discordbot >=0 <3.3.11 (fixed)) - Verified: https://github.com/advisories/GHSA-55j9-849x-26h4 (GitHub-reviewed advisory GHSA-55j9-849x-26h4 lists affected ranges: PyPI red-discordbot >=0 <3.3.11) Commands are suggestions: review each one before running it.
Loading voting…