Security readout for executives and security teams
Plain-English summary
CVE-2026-15500 is a server-side request forgery issue in AstrBot. An authenticated remote user could influence where the AstrBot server sends requests through the plugin market feature. This can matter if AstrBot can reach internal systems that ordinary users cannot. Public proof-of-concept exploit material exists, but the provided sources do not show active exploitation.
Executive priority
Treat this as a near-term remediation item, especially for internet-facing or broadly accessible AstrBot dashboards. It is not evidenced as actively exploited in the provided sources, but public exploit availability and SSRF impact justify prompt containment and upgrade planning.
Technical view
AstrBotDevs AstrBot versions 4.25.0, 4.25.1, and 4.25.2 are reported affected. The vulnerable area is get_online_plugins in astrbot/dashboard/routes/plugin.py, within the market_list endpoint. Manipulation of the custom_registry argument can cause SSRF. CVSS v2 is 6.5 with network access, low complexity, and single authentication required.
Likely exposure
Exposure is most likely where AstrBot 4.25.0 through 4.25.2 is deployed and the dashboard plugin market endpoint is reachable by authenticated users. Business risk increases if the AstrBot host can reach sensitive internal services, management interfaces, or restricted network segments.
Exploitation context
The source bundle states remote exploitation is possible and public exploit material is available. It does not state confirmed real-world exploitation, and KEV status is false. The CVSS vector indicates authentication is required, reducing drive-by exposure but not insider, compromised-account, or low-privilege-user risk.
Researcher notes
Evidence is primarily from VulDB/CVE references. The vendor reportedly did not respond, and no official patch or mitigation is named in the supplied sources. Avoid assuming all AstrBot versions are affected beyond 4.25.0 through 4.25.2 unless additional vendor evidence appears.
Mitigation direction
- Identify all AstrBot deployments and versions in use.
- Restrict dashboard and plugin market access to trusted administrators.
- Apply vendor guidance or a fixed release when available.
- Use egress filtering to limit server access to internal resources.
- Monitor AstrBot logs for unusual custom_registry or plugin market requests.
Validation and detection
- Confirm whether any deployment runs AstrBot 4.25.0, 4.25.1, or 4.25.2.
- Review who can access the dashboard and plugin market endpoint.
- Check whether the AstrBot server can reach sensitive internal-only services.
- Look for suspicious plugin market activity around July 12, 2026 onward.
- Track the CVE and vendor project for official remediation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCloud metadata behavior lookup
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.
Open ATT&CK lookupCVE-2026-15500 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.5 (2.0)
- Known Exploited
- No
- Published
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
4 official scoresWe 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.
AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR86.4VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R2.83.4VulDBCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R2.83.4VulDBCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P——VulDBVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 3.0 score
6.3MediumVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R
Base CVSS 2.0 score
6.5MediumVector: AV:N/AC:L/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:UR
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineVulDB
Advisory disclosed
- Source timelineVulDB
VulDB entry created
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineVulDB
VulDB entry last update
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- VDB-377807 | AstrBotDevs AstrBot market_list Endpoint plugin.py get_online_plugins server-side request forgeryCVE reference, VulDB · vdb-entry, technical-description
- VDB-377807 | CTI Indicators (IOB, IOC, IOA)CVE reference, VulDB · signature, permissions-required
- CVE-2026-15500 | CVE Analysis and ReportCVE reference, VulDB · third-party-advisory
- Submit #844659 | AstrBotDevs AstrBot 4.25.2 Server-Side Request Forgery (CWE-918)CVE reference, VulDB · third-party-advisory
- Submit #847481 | AstrBotDevs AstrBot 4.25.2 Server-Side Request Forgery (SSRF) (CWE-918) (Duplicate)CVE reference, VulDB · third-party-advisory
- https://gist.github.com/YLChen-007/cd162554554c273a3a7c0330aa02f3f0CVE reference, VulDB · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.