CVE-2026-85385
Last modified
CVE-2026-85385 is a critical-severity vulnerability rated 9.6/10 on the CVSS scale. 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). EPSS estimates a 0.43% chance of exploitation in the next 30 days.
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. Exploitation required concrete.misc.user_timezones to be enabled (off by default), and the unauthenticated path additionally required public registration to be enabled. The Concrete CMS security team gave this vulnerability a CVSS v4.0 score of 7.7 with 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. Thanks Suraj Bhosale for reporting.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Concretecms | Concrete Cms | < 9.5.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-85385?
How severe is CVE-2026-85385?
How do I fix CVE-2026-85385?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-8538Insufficient validation of untrusted input in GPU in Google …5.3
- CVE-2026-85380A weakness has been identified in light0011 cms c774dce31c6d…7.3
- CVE-2026-85381A security vulnerability has been detected in light0011 cms …5.3
- CVE-2026-85382A vulnerability was detected in light0011 cms c774dce31c6df0…4.3
- CVE-2026-85383A flaw has been found in itsourcecode Sales and Inventory Sy…6.3
- CVE-2026-85384A stack-based buffer overflow vulnerability exists in the ht…8.5
- CVE-2026-85386Concrete CMS before 9.5.4 did not sanitize XML and XSLT docu…6.1
- CVE-2026-85387Concrete CMS before 9.5.4 re-authorized OAuth REST API reque…7.1
- CVE-2026-85388Worklenz through 3.0.0 fails to properly validate the sort-f…8.1
- CVE-2026-85389Worklenz before 3.0.0 fails to verify task ownership by orga…6.5
- CVE-2026-8539Script injection in SanitizerAPI in Google Chrome on Android…5.4
- CVE-2026-85390Checkmate through 3.11.0 omits the isAllowed role guard midd…7.1
Are you affected by CVE-2026-85385?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
