CVE-2025-60898: An unauthenticated server-side request forgery (SSRF) vulnerability in the Thumbnail via-uri endpoint of Ha...
An unauthenticated server-side request forgery (SSRF) vulnerability in the Thumbnail via-uri endpoint of Halo CMS 2.21 allows a remote attacker to cause the server to issue HTTP requests to attacker-controlled URLs, including internal addresses. The endpoint performs a server-side GET to a user-supplied URI without adequate allow/blocklist validation and returns a 307 redirect that can disclose internal URLs in the Location header.
Security readout for executives and security teams
Plain-English summary
CVE-2025-60898 is a reported unauthenticated SSRF issue in Halo CMS 2.21. A remote user could make the server fetch a supplied URL, including internal addresses, and a redirect response may reveal internal URLs. Business impact is mainly information exposure and internal network probing, not direct code execution based on the provided sources.
Executive priority
Treat as a moderate exposure issue. Prioritize internet-facing Halo CMS instances, especially where the CMS can reach internal services. This is less urgent than active RCE, but it can weaken network segmentation and disclose internal service locations.
Technical view
The Thumbnail via-uri endpoint reportedly performs a server-side GET to a user-controlled URI without adequate allow/blocklist validation. The CVSS 3.1 score is 5.8 with network attack vector, no privileges, no user interaction, changed scope, and low confidentiality impact. Product/version metadata is incomplete beyond the description naming Halo CMS 2.21.
Likely exposure
Highest concern is public or partner-accessible Halo CMS 2.21 deployments where the Thumbnail via-uri endpoint can be reached without authentication. The source bundle does not establish affected version ranges beyond Halo CMS 2.21.
Exploitation context
The CVE is not listed as KEV, and the provided sources do not cite active exploitation. The public description indicates unauthenticated remote reachability, but available evidence supports SSRF and URL disclosure only, not confirmed data theft or code execution.
Researcher notes
Evidence is limited. The CVE record identifies CWE-918 and CVSS 5.8, while the affected product fields are n/a. The narrative names Halo CMS 2.21 and the Thumbnail via-uri endpoint. Avoid broad affected-version claims until vendor or CNA data confirms them.
Mitigation direction
Check Halo CMS vendor guidance for fixed versions or official workarounds.
Restrict unauthenticated access to the Thumbnail via-uri endpoint where feasible.
Enforce outbound filtering from the CMS host to internal and private address ranges.
Review reverse proxy and application controls for URL validation on thumbnail requests.
Monitor CMS logs for unusual thumbnail URI requests and redirect patterns.
Validation and detection
Inventory Halo CMS deployments and confirm whether version 2.21 is present.
Determine whether the Thumbnail via-uri endpoint is reachable without authentication.
Review application logs for user-supplied thumbnail URLs targeting internal addresses.
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.
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.