This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Craft Cms
Craft CMS 4.2.0.1 is affected by Cross Site Scripting (XSS) in the file src/web/assets/cp/src/js/BaseElementSelectInput.js and in specific on the line label: elementInfo.label. (2022-09-21, CVE-2022-37246)
Craft CMS 4.2.0.1 is vulnerable to Cross Site Scripting (XSS) via Drafts. (2022-09-16, CVE-2022-37251)
Craft CMS 4.2.0.1 is vulnerable to stored a cross-site scripting (XSS) via /admin/settings/fields page. (2022-09-16, CVE-2022-37247)
Craft CMS 4.2.0.1 is vulnerable to Cross Site Scripting (XSS) via src/helpers/Cp.php. (2022-09-16, CVE-2022-37248)
Craft CMS 4.2.0.1 suffers from Stored Cross Site Scripting (XSS) in /admin/myaccount. (2022-09-16, CVE-2022-37250)
Craft CMS before 3.7.29 allows XSS. (2022-04-03, CVE-2022-28378)
An issue was discovered in Craft CMS before 3.6.0. In some circumstances, a potential XSS vulnerability existed in connection with front-end forms that accepted user uploads. (2021-06-30, CVE-2021-27902)
Craft CMS before 3.6.13 has an XSS vulnerability. (2021-05-07, CVE-2021-32470)
Cross Site Scripting (XSS) vulnerability in craftcms 3.1.31, allows remote attackers to inject arbitrary web script or HTML, via /admin/settings/sites/new. (2021-03-26, CVE-2020-19626)
In the 3.1.12 Pro version of Craft CMS, XSS has been discovered in the header insertion field when adding source code at an s/admin/entries/news/new URI. (2019-12-31, CVE-2019-9554)
Craft CMS before 3.3.8 has stored XSS via a name field. This field is mishandled during site deletion. (2019-10-11, CVE-2019-17496)
Craft CMS before 3.1.31 does not properly filter XML feeds and thus allowing XSS. (2019-06-18, CVE-2019-12823)
index.php?p=admin/actions/entries/save-entry in Craft CMS 3.0.25 allows XSS by saving a new title from the console tab. (2018-12-24, CVE-2018-20418)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>