Ckeditor XSS Vulnerability
Published 21 Nov 2018 · Updated 16 Feb 2024
Affected packages
- Affected
- <4.11.0
- Fixed in
- 4.11.0
npm install ckeditor@4.11.0- Affected
- >=8.0.0 <8.7.21
- Fixed in
- 8.7.21
composer require typo3/cms-core:^8.7.21- Affected
- >=9.0.0 <9.5.2
- Fixed in
- 9.5.2
composer require typo3/cms-core:^9.5.2- Affected
- >=8.0.0 <8.7.21
- Fixed in
- 8.7.21
composer require typo3/cms:^8.7.21- Affected
- >=9.0.0 <9.5.2
- Fixed in
- 9.5.2
composer require typo3/cms:^9.5.2Details
CKEditor 4.x before 4.11.0 allows user-assisted XSS involving a source-mode paste. It was possible to execute XSS inside the CKEditor source area after persuading the victim to: (i) switch CKEditor to source mode, then (ii) paste a specially crafted HTML code, prepared by the attacker, into the opened CKEditor source area, and (iii) switch back to WYSIWYG mode. Although this is an unlikely scenario, it is recommended to upgrade to the latest editor version.
Is GHSA-g68x-vvqq-pvw3 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 ckeditor, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2018-17960
- Linkckeditor.com/blog/CKEditor-4.11-with-emoji-dropdown-and-auto-link-on-typing-released
- Linkckeditor.com/cke4/release/CKEditor-4.11.0
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2018-17960.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2018-17960.yaml
- Advisorygithub.com/advisories/GHSA-g68x-vvqq-pvw3
- Linktypo3.org/security/advisory/typo3-core-sa-2018-005
- Linkweb.archive.org/web/20200227030123/http://www.securityfocus.com/bid/109205
- Linkwww.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.