Cross site scripting in Concrete CMS
Published 25 Jun 2022 · Updated 8 Nov 2023
Affected packages
- Affected
- >=9.0.0 <9.1.0
- Fixed in
- 9.1.0
composer require concrete5/core:^9.1.0- Affected
- <8.5.8
- Fixed in
- 8.5.8
composer require concrete5/core:^8.5.8Details
XSS in /dashboard/blocks/stacks/view_details/ - old browsers only. When using an older browser with built-in XSS protection disabled, insufficient sanitation where built urls are outputted can be exploited for Concrete 8.5.7 and below as well as Concrete 9.0 through 9.0.2 to allow XSS. This cannot be exploited in modern-day web browsers due to an automatic input escape mechanism. Concrete CMS Security team ranked this vulnerability 3.1with CVSS v3.1 Vector AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N. Sanitation has been added where built urls are output.
Is GHSA-m2ww-6wv6-vw3c in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected concrete5/core, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-30120
- Linkhackerone.com/reports/1363598
- Linkdocumentation.concretecms.org/developers/introduction/version-history/858-release-notes
- Linkdocumentation.concretecms.org/developers/introduction/version-history/910-release-notes
- Packagegithub.com/concretecms/concretecms-core
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.