External risk intelligence

PublicCMS SSRF in Chat Interface

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2025-65836

PublicCMS is a content management system designed to be deployed as a web application. The vulnerability resides in a chat interface component which is part of the administrative or user-facing web functionality, making it commonly accessible via the public internet when the CMS is deployed in its standard configuration.

Server-Side Request Forgery

Publiccms

5.202506.b

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability, identified in PublicCMS, involves a flaw in the chat interface that could allow unauthorized access to internal systems. This type of vulnerability, known as Server-Side Request Forgery (SSRF), can potentially expose sensitive information or disrupt operations by tricking the application into making unintended requests on behalf of an attacker. Given its critical severity and network-exploitable nature, understanding its presence within your environment is important.

A chat feature flaw allows unauthorized internal access.
Critical severity, network-exploitable, impacting web applications.
Confirm relevance; understand potential access risks.

Attack Path

How an attacker could exploit the issue

An attacker can target the chat interface within PublicCMS's administrative features. This vulnerability, identified in the SimpleAiAdminController, allows for Server-Side Request Forgery (SSRF), potentially enabling unauthorized access to internal resources or sensitive data.

Open network access required.
Chat interface trigger.
Data exposure and manipulation risk.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to interact with the chat interface and potentially cause the affected system to make unintended network requests. The system's behavior could be altered when supported by the advisory.

System network requests could be compromised.
Network requests may be made to unintended locations.
Service behavior may be altered.

Operational Fix

Recommended remediation, mitigation, and detection steps

Given the vulnerability in PublicCMS's chat interface, the platform or application owners are likely responsible for its remediation. The immediate first step involves discovering all instances of the affected technology, confirming its accessibility and business criticality, and then identifying the precise owner to initiate a risk-based remediation plan.

Platform and application owners.
Confirm reachability and business criticality.
Plan remediation based on assessed risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is PublicCMS?

PublicCMS is a Java-based open-source content management system used to build and manage dynamic websites. It provides various administrative and user-facing modules, including AI-driven chat interfaces, to help site administrators manage content or interact with visitors. Because it functions as a web application, it is typically hosted on servers that are reachable via a browser, allowing users or administrators to interact with its features over the network.

How does CVE-2025-65836 work?

This vulnerability is a Server-Side Request Forgery (SSRF), categorized as CWE-918. It means the application can be tricked into making network requests to unintended destinations. By manipulating the chat interface, an attacker can force the server to fetch data from internal systems or network locations that are normally protected from the outside, potentially exposing sensitive information or interacting with internal services.

When is the chat interface vulnerable?

The flaw exists specifically within the SimpleAiAdminController. An attacker triggers the issue by sending specific inputs to this chat interface. It is important to note that the vulnerability relies on the application's ability to process these requests; simply browsing the site or using unrelated parts of the CMS does not necessarily trigger this specific defect.

Is my PublicCMS instance at risk?

If your instance is reachable from the internet, it is at higher risk. According to Halo Surface Signal, this vulnerability resides in a component often exposed publicly, making it easier for remote attackers to attempt exploitation. Systems positioned behind restrictive firewalls or those that are not accessible to the public internet generally have a reduced likelihood of successful external targeting.

What should I do to address this issue?

Begin by identifying every instance of PublicCMS running in your environment to understand your total footprint. Once located, verify if the specific version 5.202506.b is in use. Coordinate with your technical team to confirm how these instances are exposed to the network and determine their business importance, then prioritize them for updates or security configurations to mitigate the risk posed by the chat interface.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.