MediumGHSA-pp74-g2q5-j4jfBIT-silverstripe-2022-37421CVE-2022-37421
Silverstipe CMS Stored XSS in custom meta tags
Published 21 Nov 2022 · Updated 20 Feb 2024
Affected package
silverstripe/cmsComposer
- Affected
- >=4.0.0 <4.11.3
- Fixed in
- 4.11.3
Update to the fixed version for your release line, for example:
composer require silverstripe/cms:^4.11.3Details
A malicious content author could create a custom meta tag and execute an arbitrary JavaScript payload. This would require convincing a legitimate user to access a page and enter a custom keyboard shortcut. This requires CMS access to exploit.
Is GHSA-pp74-g2q5-j4jf 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 silverstripe/cms, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-37421
- Linkforum.silverstripe.org/c/releases
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/cms/CVE-2022-37421.yaml
- Linkwww.silverstripe.org/blog/tag/release
- Linkwww.silverstripe.org/download/security-releases
- Linkwww.silverstripe.org/download/security-releases/cve-2022-37421
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.