Skip to content

Concrete CMS vulnerable to stored XSS via the Role Name field

Low severity GitHub Reviewed Published Feb 9, 2024 to the GitHub Advisory Database • Updated Feb 15, 2024

Package

composer concrete5/concrete5 (Composer)

Affected versions

>= 9.0.0RC1, < 9.2.5

Patched versions

9.2.5

Description

Concrete CMS version 9 before 9.2.5 is vulnerable to  stored XSS via the Role Name field since there is insufficient validation of administrator provided data for that field. A rogue administrator could inject malicious code into the Role Name field which might be executed when users visit the affected page. The Concrete CMS Security team scored this 2 with CVSS v3 vector AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator . Concrete versions below 9 do not include group types so they are not affected by this vulnerability.

References

Published by the National Vulnerability Database Feb 9, 2024
Published to the GitHub Advisory Database Feb 9, 2024
Reviewed Feb 9, 2024
Last updated Feb 15, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.045%
(15th percentile)

Weaknesses

CVE ID

CVE-2024-1247

GHSA ID

GHSA-q25h-jch8-gfrp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.