A security vulnerability has been detected in AstrBotDevs AstrBot up to 4.25.2. Affected by this issue is the function ToolsRoute.test_mcp_connection of the file astrbot/dashboard/routes/tools.py of the component MCP Test Endpoint. The manipulation of the argument mcp_server_config.url leads to server-side request forgery. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Security readout for executives and security teams
Plain-English summary
CVE-2026-15501 is a server-side request forgery issue in AstrBot’s MCP Test Endpoint. An authenticated remote user may be able to make the AstrBot server send unintended requests. This can expose internal services or data reachable from the server. Public exploit material exists, but the provided sources do not show confirmed active exploitation.
Executive priority
Treat as a near-term remediation item for internet-exposed or multi-user AstrBot deployments. The issue is not currently KEV-listed, but public exploit material and potential internal-network access make access restriction and monitoring important now.
Technical view
AstrBotDevs AstrBot 4.25.0, 4.25.1, and 4.25.2 are affected. The issue is in ToolsRoute.test_mcp_connection in astrbot/dashboard/routes/tools.py, where mcp_server_config.url can be manipulated to trigger SSRF. VulDB rates it CVSS 2.0 score 6.5 with network access, low complexity, and authentication required.
Likely exposure
Risk is highest where the AstrBot dashboard or MCP testing capability is reachable by untrusted or broadly privileged users. Authentication is required according to the CVSS vector, reducing opportunistic exposure but not insider, compromised-account, or weak-access-control risk.
Exploitation context
The vulnerability is remotely reachable and a public exploit reference is listed. However, CISA KEV status is false in the provided bundle, and no cited source confirms active exploitation in the wild.
Researcher notes
Evidence is primarily from VulDB and CVE records. The source bundle states the vendor was contacted but did not respond. No official patch, workaround, or vendor advisory is identified in the provided sources, so remediation guidance should remain conservative.
Mitigation direction
Check AstrBotDevs or project channels for official remediation guidance or fixed versions.
Restrict dashboard and MCP test endpoint access to trusted administrators only.
Apply network egress controls from AstrBot servers to internal and sensitive services.
Disable or limit MCP test functionality if it is not operationally required.
Monitor for unusual outbound requests originating from AstrBot hosts.
Validation and detection
Inventory AstrBot deployments and confirm whether versions 4.25.0 through 4.25.2 are present.
Verify whether the dashboard and MCP test endpoint are exposed beyond trusted administrators.
Review access logs for MCP test endpoint activity by unexpected users.
Review outbound network logs from AstrBot hosts for unusual internal destination requests.
Track vendor advisories and re-test after any official update is applied.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
0ADP providers
6Source links
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.