Concrete CMS v.9.2.1, a widely-used content management system (CMS), has been identified to contain multiple Cross Site Scripting (XSS) vulnerabilities that could enable attackers to execute arbitrary code through a carefully-designed Header and Footer tracking script. Notably, the vendor disputes the validity of this vulnerability, arguing that changes to the header and footer can only be made by an admin, and the feature to place JavaScript in these areas is an intentional customization feature. Furthermore, the exploitation method claimed by "sromanhu" is not believed to compromise a Concrete CMS session, owing to the configuration of the Concrete CMS session cookie as HttpOnly.

Code Snippet

The following code illustrates the injection of a malicious script into the Header and Footer Tracking Codes of the SEO & Statistics in Concrete CMS v.9.2.1:

<script>alert('XSS Vulnerability')</script>

Exploit Details

The vulnerability lies in the lack of proper input sanitization and output encoding, which allows an attacker to inject malicious JavaScript code into the Header and Footer Tracking Codes of the SEO & Statistics section in Concrete CMS v.9.2.1. Once injected, the arbitrary code is executed whenever a user with administrator privileges visits a web page containing these tracking codes. This could result in the theft of sensitive information, modification of user data, or further spread malicious scripts across the application.

References to Original Sources

1. CVE-2023-44760 — A comprehensive overview of the CVE from The MITRE Corporation, an organization that maintains and updates the CVE database.

2. Concrete CMS v.9.2.1 — The official website for the Concrete CMS project where users can download the software, access documentation, and participate in the community forums.

3. sromanhu's Disclosure — The original vulnerability disclosure from security researcher "sromanhu," detailing the Header and Footer XSS vulnerability in Concrete CMS v.9.2.1.


In conclusion, Concrete CMS v.9.2.1 has been identified to harbor multiple Cross Site Scripting (XSS) vulnerabilities, particularly with regards to its Header/Footer tracking codes. While the vendor disputes the existence of this vulnerability due to its intentional customization feature, as well as the HttpOnly session cookie configuration, users should remain vigilant about potential injection of malicious scripts. To mitigate risk, administrators should validate and sanitize inputs, while also applying proper output encoding techniques to prevent malicious code execution. Regularly updating, patching, and monitoring the CMS will also contribute to a more secure environment.


Published on: 10/23/2023 22:15:09 UTC
Last modified on: 11/15/2023 22:15:27 UTC