CVE-2024-8660: Concrete CMS Top Navigator Bar Block Stored XSS Vulnerability

concrete5/concrete5 Updated 02 Oct 2025

Summary

17/09/2024
Yes i
Moderate
4.8

CVE-2024-8660: Concrete CMS stored XSS vulnerability in the "Top Navigator Bar" block. Affects concrete5/concrete5 versions >= 9.0.0, < 9.3.3. Fixed in 9.3.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Concrete CMS is an open-source content management system that allows users to build and manage websites with ease. It features a user-friendly interface, customizable themes, and a variety of add-ons. The Top Navigator Bar block is a key component that enables site administrators to create a navigation menu for their websites. However, versions 9.0.0 through 9.3.3 of Concrete CMS are vulnerable to a stored XSS (Cross-Site Scripting) attack due to insufficient sanitization of user inputs in this block.

Vulnerability Detail

The stored XSS vulnerability in Concrete CMS arises from the Top Navigator Bar block not properly sanitizing the output. This flaw allows a malicious administrator to inject harmful scripts that execute when targeted users visit the home page. The potential ramifications include unauthorized access to user data, session hijacking, and defacement of the website. This vulnerability affects only versions 9.0.0 to 9.3.3, as earlier versions do not include the Top Navigator Bar block.

How To Fix

Minimum fixed version

9.3.3

This is the first release that contains the fix.

composer require concrete5/concrete5:9.3.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If immediate upgrading is not possible, consider disabling the Top Navigator Bar block until a patch can be applied. This can be done by removing the block from your site’s layout or restricting access to it for non-administrative users.

Conclusion

The stored XSS vulnerability in the Top Navigator Bar block of Concrete CMS poses a significant risk to users of versions 9.0.0 through 9.3.3. It is crucial to update to version 9.3.4 or later to ensure the security of your website. Additionally, utilizing tools like Vulert can help monitor and alert you to potential vulnerabilities in your open-source software.

See every vulnerability recorded for concrete5/concrete5 →

Share this vulnerability

FAQ

Stored XSS is a type of security vulnerability where an attacker can inject malicious scripts into a web application, which are then stored on the server and executed when other users access the affected page.

If you are using Concrete CMS versions 9.0.0 to 9.3.3, your installation is vulnerable. You can check your version in the dashboard or by running 'composer show concrete5/concrete5'.

Failing to address this vulnerability can lead to data breaches, unauthorized access to user accounts, and damage to your website's reputation.

Yes, Vulert can monitor your application for open-source vulnerabilities using your composer.lock file, providing real-time alerts without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Related vulnerabilities

Recent vulnerabilities recorded for concrete5/concrete5.

How To Fix

Minimum fixed version

9.3.3

This is the first release that contains the fix.

composer require concrete5/concrete5:9.3.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback