Quick answers
- Is CVE-2025-60898 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-60898 being exploited in the wild.
- How severe is CVE-2025-60898?
- Medium severity, with a CVSS score of 5.8, published 29 October 2025.
- Which products and versions are affected?
- Halo 2.21.
- Is there a fix for CVE-2025-60898?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-60898 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-60898?
- Check whether you run Halo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An unauthenticated Server-Side Request Forgery (SSRF) vulnerability exists in the 'Thumbnail via-uri' endpoint of Halo CMS version 2.21. The root cause is a failure to adequately validate user-supplied URIs against an allowlist or blocklist before performing a server-side GET request. An attacker can exploit this by providing a malicious URI, causing the server to interact with internal network resources or external attacker-controlled infrastructure. The endpoint further facilitates information disclosure by returning a 307 redirect that may reveal internal URLs within the Location header. This vulnerability is reachable over the network without authentication.
Affected products
- Halo Halo CMS 2.21
Timeline
- 2025-10-29: advisory: NVD publication date