CVE-2025-67349
Cross-Site Scripting in FluentCMS 1.2.3 Admin Add Page
Publication date: 2025-12-26
Last updated on: 2025-12-26
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fluentcms | fluentcms | 1.2.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a cross-site scripting (XSS) issue in FluentCMS version 1.2.3. It occurs when an admin user uses the "Add Page" function, where the application does not properly sanitize input in the <head> section of the page. This allows remote attackers to inject arbitrary script tags, potentially executing malicious scripts in the context of the admin's browser session.
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary scripts in the admin's browser, which could lead to session hijacking, unauthorized actions performed with admin privileges, data theft, or the injection of malicious content into the CMS-managed pages.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the admin 'Add Page' function for improper input sanitization in the <head> section. Specifically, you can attempt to inject script tags in the input fields after logging in as an admin and observe if the scripts are executed or reflected unsanitized. There are no specific commands provided in the resources, but manual testing or using web vulnerability scanners that test for reflected XSS on admin pages can help detect this issue. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing proper input validation and output encoding on both the frontend and backend components of FluentCMS, especially for the admin 'Add Page' function. Restricting or sanitizing input to prevent injection of script tags in the <head> section is critical. Additionally, avoid clicking on suspicious URLs that may exploit this reflected XSS vulnerability. [2]