CVE-2025-65837
Cross-Site Scripting in PublicCMS Content Search Module
Publication date: 2025-12-22
Last updated on: 2025-12-22
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| publiccms | publiccms | 5.202506.b |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-65837 is a Cross Site Scripting (XSS) vulnerability in PublicCMS version V5.202506.b, specifically in the Content Search module. It occurs when a low-privilege user with content editing permissions creates content with a malicious name. This malicious input triggers the XSS vulnerability during the content search process, allowing execution of arbitrary scripts. [2]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute scripts that steal sensitive information, such as super administrator credentials. For example, an attacker can steal the CSRF token via a crafted GET request to the admin interface. This enables privilege escalation despite the attacker starting with limited permissions, posing a significant security risk. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to steal sensitive information such as super administrator credentials and CSRF tokens through Cross Site Scripting (XSS). This unauthorized access and potential data breach could lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive data and preventing unauthorized access. Therefore, exploitation of this vulnerability may result in violations of these standards due to compromised confidentiality and integrity of protected information. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring for suspicious GET requests to the admin interface, specifically crafted to exploit the XSS in the Content Search module. For example, look for unusual requests to admin/index.html with parameters that might include malicious scripts. Using tools like curl or wget, you can simulate such requests to test if the system is vulnerable. Example command: curl -v 'http://your-publiccms-site/admin/index.html?search=<script>alert(1)</script>'. Additionally, reviewing logs for unexpected script injections or unusual content names created by low-privilege users can help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting content editing permissions to trusted users only, especially limiting who can create or modify content names. Implement input validation and sanitization on the Content Search module to prevent malicious scripts from being processed. Additionally, monitor and block suspicious requests to the admin interface, and consider applying any available patches or updates from PublicCMS that address this vulnerability. If patches are not yet available, consider disabling the vulnerable Content Search module or restricting access to it until a fix is applied. [2]