Stored XSS via unencoded attribute-set names
Published Aug 8, 2024 · Updated Sep 25, 2025
Stored XSS in Concrete CMS before 8.5.18 and 9.0.0 through 9.3.2 allows remote authenticated users to run script in another user's browser. Attribute-set views rendered getAttributeSetName() output directly in an HTML heading and form value; crafted stored names therefore remained executable markup. Administrator privileges are required to save the name, and another user must open an affected view, allowing the script to read data available to that user's browser.
Summary
What happened
Stored XSS in Concrete CMS before 8.5.18 and 9.0.0 through 9.3.2 allows remote authenticated users to run script in another user's browser. Attribute-set views rendered getAttributeSetName() output directly in an HTML heading and form value; crafted stored names therefore remained executable markup. Administrator privileges are required to save the name, and another user must open an affected view, allowing the script to read data available to that user's browser.
The record
- CVE
- CVE-2024-7394
- Published
- Aug 8, 2024
- Updated
- Sep 25, 2025
- Vendor
- Concrete CMS
- Product
- Concrete CMS
- Classifications
- CWE-79, CAPEC-592, T1203
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Aug 8, 2024CVE publishedPublication date reported by the CVE source.
- Sep 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5 <8.5.18
- Affected versionversion=9 <9.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo