Servers and applications
CVE-2026-85385
Concrete CMS below 9.5.4 did not validate the user timezone value (uTimezone) on write and rendered it without output encoding on the Dashboard user management page, where Date::getTimezoneDisplayName() returns any non-IANA value unchanged. A stored cross-site scripting payload saved in this field executed in an administrator's browser when they viewed the affected user in the Dashboard, running…
- Severity
- High 7.7
- Published
- 16 Sept 2026
- Last changed
- 21 Sept 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 9.5.4
- Exploit chance
- 0.6% in the next 30 daysHigher than 47% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Cross-site scripting (CWE-79)
- Attack
- Over the network · Only under certain conditions · No login needed · Needs someone to view a page or file
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Sources
- NVD
Description
Concrete CMS below 9.5.4 did not validate the user timezone value (uTimezone) on write and rendered it without output encoding on the Dashboard user management page, where Date::getTimezoneDisplayName() returns any non-IANA value unchanged. A stored cross-site scripting payload saved in this field executed in an administrator's browser when they viewed the affected user in the Dashboard, running script in the admin session (for example to read CSRF tokens, create administrator accounts, or change site settings). In Concrete CMS 9.5.3 the field became reachable by unauthenticated visitors through public registration; in Concrete CMS below 9.5.3, the same field was reachable by any authenticated user through the account profile editor.
Affected software
| Software | Affected versions |
|---|---|
Concrete CMSServers and applications · cpe:a:concretecms:concrete_cms |
|
About Concrete CMS
free software content management system written in PHP
- Monthly downloads (Packagist)
- 171Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 2,983Packagist, 15 Nov 2026
- GitHub stars
- 855GitHub, 15 Nov 2026
- Forks
- 491GitHub, 15 Nov 2026
- Latest release
- 9.5.7GitHub, 15 Nov 2026
- Released
- 20 Oct 2026GitHub
- License
- MIT LicenseWikidata
- Written in
- PHPWikidata
- First published on GitHub
- 22 Apr 2014GitHub
Vulnerabilities in Concrete CMS
- In our list
- 198
- Published in the last 12 months
- 95
- Critical, last 12 months
- 1
- High, last 12 months
- 25
- Known exploited
- 0
- CVE-2026-85387Concrete CMS before 9.5.4 re-authorized OAuth REST API requests from the bearer token alone and did not re-check the state of the account the token had been issued to. The resource server's authorization validator confirmed only that a token existed, had not expired, and had not been explicitly revoked, and deactivating a user did not revoke that user's outstanding tokens. As a result, a…Low 2.0 16 Sept 2026
- CVE-2026-18120Concrete CMS before 9.5.3 exposed a legacy Express entry search endpoint that returned entry result JSON without invoking the canViewExpressEntries() permission check applied by the normal dashboard and CSV Export flow. An unauthenticated visitor who knew or discovered an Express entity identifier could enumerate that entity's entry search results, disclosing attribute values intended to be…Medium 6.3 16 Sept 2026
- CVE-2026-87031n Concrete CMS 9.2.0 through 9.5.3, the REST API user creation endpoint (POST /ccm/api/1.0/users, the add() method of concrete/src/Api/Controller/Users.php) did not perform a permission check before creating an account. As a result, any valid OAuth token carrying the users:add scope, including a client_credentials token with no associated user context, could create active, validated user…Low 2.1 16 Sept 2026
- CVE-2026-87028Concrete CMS 9 through 9.5.3 did not confirm that a board InstanceItem submitted to the custom-slot preview endpoint belonged to the board instance the requesting user was authorized to edit, and did not enforce page-view permission before generating page-backed summary content. As a result, an authenticated user holding edit-board-contents permission on a single board instance could submit the…Medium 5.3 16 Sept 2026
- CVE-2026-85386Concrete CMS before 9.5.4 did not sanitize XML and XSLT documents uploaded through a public Form Block file-upload question. Plain XML uploads were validated by file extension only and stored as publicly accessible files that were served inline from the application's own origin. An unauthenticated visitor could therefore store an XML document containing an xml-stylesheet processing instruction…High 7.3 16 Sept 2026
- CVE-2026-81927Concrete CMS before 9.5.3 contained a stored cross-site scripting vulnerability in SVG file handling. When SVG processing was set to the non-default "Reject files containing potentially harmful elements" mode (concrete.file_manager.images.svg_sanitization.action = reject), uploaded SVGs were checked only against a small built-in blocklist covering the script element and on* event-handler…Low 1.8 15 Sept 2026