CVE-2026-15500 in AstrBot
Summary
by MITRE • 07/12/2026
A weakness has been identified in AstrBotDevs AstrBot up to 4.25.2. Affected by this vulnerability is the function get_online_plugins of the file astrbot/dashboard/routes/plugin.py of the component market_list Endpoint. Executing a manipulation of the argument custom_registry can lead to server-side request forgery. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 07/12/2026
This vulnerability exists within AstrBotDevs AstrBot version 4.25.2 and earlier, specifically targeting the get_online_plugins function located in astrbot/dashboard/routes/plugin.py. The flaw resides in the market_list endpoint where the custom_registry parameter is processed without adequate input validation or sanitization. This oversight creates a critical server-side request forgery vulnerability that allows remote attackers to manipulate the registry argument and potentially execute unauthorized requests to arbitrary servers. The vulnerability represents a classic srfi-2018-0043 pattern where insufficient parameter validation leads to unauthorized network access, making it particularly dangerous in web applications that handle external resource fetching.
The technical implementation of this flaw demonstrates poor input handling practices that align with CWE-918, Server-Side Request Forgery, and specifically CWE-798, Use of Hard-coded Credentials, when considering the registry manipulation aspect. Attackers can exploit this by crafting malicious requests that redirect the application's network traffic to unintended destinations, potentially allowing them to access internal systems, exfiltrate data, or perform unauthorized operations against other services within the network perimeter. The remote execution capability means that an attacker needs only to send a specially crafted request to the vulnerable endpoint without requiring physical access or local privileges.
The operational impact of this vulnerability extends beyond simple data theft, as it can enable attackers to establish persistent access points or launch further attacks against the internal infrastructure. This weakness significantly increases the attack surface for organizations using AstrBot, particularly those that rely on external plugin repositories or have complex network architectures where the application might need to communicate with various services. The lack of vendor response following early disclosure indicates potential security governance issues within the project, leaving users exposed to ongoing threats without official patches or mitigation guidance.
Organizations should immediately implement network-level restrictions to prevent outbound connections to untrusted domains, deploy web application firewalls to monitor and block suspicious requests, and consider disabling the affected plugin market functionality until a proper patch is available. The vulnerability's public exploit availability means that automated attacks could be occurring, making immediate remediation essential. Security teams should also conduct comprehensive network monitoring to detect any unusual outbound traffic patterns that might indicate exploitation attempts, while implementing proper input validation measures to prevent similar issues in other components of the application stack. This incident highlights the importance of continuous security assessment and vendor communication in maintaining secure software ecosystems.