Technical impact
The vulnerability allows an attacker with no credentials to fabricate an admin session cookie by using the hard‑coded default session key 'muse_bot_session_key'. The forged cookie carries any chosen user_id and grants full administrative privileges over the web interface, enabling the attacker to read password hashes, chat logs, and bot configuration, as well as stop or reboot bots. This results in a complete compromise of confidentiality and integrity of the bot system.
Affected Systems
All versions of MuseBot earlier than 2.0.0, released by Yincongcyincong, are affected according to the vendor's advisories. The defect is in the admin configuration file and login controller that use a hard‑coded session key.
Risk and Exploitability
The CVSS score of 9.3 indicates a critical vulnerability. The EPSS score is unavailable, but the lack of a KEV listing does not reduce the severity. Attackers can exploit the flaw remotely by sending an HTTP request with a forged cookie to the admin endpoint; the required precondition is the presence of the default session key in the configuration, which is always set in affected releases. Therefore the risk level is high and the attack is straightforward for anyone with network access to the bot instance.