CVE-2023-48650 json
Concrete CMS Stored XSS in Layout Preset Name
published 2023-12-25 2 y ago modified 2026-06-17 4 mo ago also GHSA-x577-gcc9-9xjj , EUVD-2024-0758
- cvss
- 4.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
Concrete CMS before 8.5.14 and 9 before 9.2.3 is vulnerable to an admin adding a stored XSS payload via the Layout Preset name.
Patch / fix
- packagist concrete5/concrete5 8.5.14, 9.2.3
- concretecms concrete_cms 8.5.14, 9.2.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | concrete5/concrete5 | <8.5.14 >=9.0.0, <9.2.3 |
8.5.14 9.2.3 |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/concretecms/concretecms/commit/077755e6bbbc1c67b7508add9e3d207e8d8909a0
web
-
github.com
/concretecms/concretecms/commit/5b93470bcccf271810d3a0b190368ce6a9d6c84b
web
-
concretecms.org
/about/project-news/security/2023-12-05-concrete-cms-new-cves-and-cve-updates
web, vendor-advisory
-
documentation.concretecms.org
/developers/introduction/version-history/923-release-notes
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2023-48650
advisory
-
github.com
/concretecms/concretecms
package
Sources
- CVE List CVE-2023-48650
- GitHub Advisory GHSA-x577-gcc9-9xjj
- NVD CVE-2023-48650
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.