CVE-2025-53943: Death1Clown VoidBot_open-source · Incorrect Authorization
Affects Death1Clown VoidBot_open-sourceSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 1.0.0 or 0.8.2 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.0, 0.8.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade death1clown/VoidBot_open-source to 1.0.0 or 0.8.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdeath1clown/VoidBot_open-sourcepkg:github/death1clown/VoidBot_open-sourceOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Immediate upgrade to VoidBot Open-Source version 1.0.0 or later, where the authorization checks have been properly implemented and the vulnerability fixed. 2. Conduct an audit of all Discord bots in use within the organization to identify any instances of VoidBot Open-Source versions prior to 1.0.0. 3. Implement strict role and permission management within Discord servers to limit the number of users with administrative privileges, reducing the potential impact of compromised or malicious accounts. 4. Monitor Discord server logs for unusual administrative command usage, such as unexpected bans, kicks, or shutdown commands, to detect potential exploitation attempts early. 5. Consider deploying additional bot security layers or custom wrappers that enforce authorization independently of the bot’s internal checks, especially if upgrading is delayed. 6. Educate server administrators and moderators about the vulnerability and encourage vigilance regarding suspicious user behavior. 7. Regularly review and update bot configurations and permissions following best practices to minimize attack surface.
Description
VoidBot Open-Source is a customizable Discord bot. VoidBot Open-Source versions 0.0.1 through 0.8.1 contain a vulnerability in the command handler where permission checks are not properly enforced for certain administrative commands. This allows users without the required roles or privileges to execute sensitive commands such as `ban`, `kick`, or `shutdown`, potentially disrupting server operations. Version 1.0.0 fixes the issue.