Craft CMS vulnerable to stored XSS in breadcrumb list and title fields
Published 9 Sept 2024 · Updated 9 Sept 2024
Affected package
- Affected
- >=5.0.0 <5.1.2
- Fixed in
- 5.1.2
composer require craftcms/cms:^5.1.2Details
Summary
Multiple Stored XSS can be triggered by the breadcrumb list and title fields with user input.
Details
1. In the /admin/categories page, category title isn't sanitized and triggered xss. 2. In the category edit page under the /admin/categories/, category title in breadcrumb list isn't sanitized and triggered xss. 3. In the /admin/entries page, entry title isn't sanitized and triggered xss. 4. In the entry edit page under the /admin/entries/, entry title in breadcrumb list isn't sanitized and triggered xss. 5. In the /admin/myaccount and pages under it, username or full name in breadcrumb list isn't sanitized and triggered xss.
Impact
Malicious users can tamper with the control panel.
PoC
1. In the /admin/categories page, category title isn't sanitized and triggered xss.
1. Access to the Settings -> Categories ( /admin/settings/categories )
2. Create new category group
3. Access to the Categories page ( /admin/categories/ )
4. Push the New category button
5. Input the Title column : xss<script>alert('xss')</script>
6. Push the Create Category or Save button
7. Access to the Categories page again and it triggers xss2. In the category edit page under the /admin/categories/, category title in breadcrumb list isn't sanitized and triggered xss.
1. Access to the Settings -> Categories ( /admin/settings/categories )
2. Create new category group
3. Access to the Categories page ( /admin/categories/ )
4. Push the New category button
5. Input the Title column : xss<script>alert('xss')</script>
6. Push the Create Category or Save button
7. Access to the Category edit page again and it triggers xss3. In the /admin/entries page, entry title isn't sanitized and triggered xss.
1. Access to the Settings -> Entry Types ( /admin/settings/entry-types )
2. Create new entry type
3. Access to the Settings -> Sections ( /admin/settings/sections )
4. Create new section
5. Access to the Entries page ( /admin/entries )
6. Push the New entry button
7. Input the Title column : xss<script>alert('xss')</script>
8. Push the Create entry or Save button
9. Access to the Entries page again and it triggers xss4. In the entry edit page under the /admin/entries/, entry title in breadcrumb list isn't sanitized and triggered xss.
1. Access to the Settings -> Entry Types ( /admin/settings/entry-types )
2. Create new entry type
3. Access to the Settings -> Sections ( /admin/settings/sections )
4. Create new section
5. Access to the Entries page ( /admin/entries )
6. Push the New entry button
7. Input the Title column : xss<script>alert('xss')</script>
8. Push the Create entry or Save button
9. Access to the Entriy edit page again and it triggers xss5. In the /admin/myaccount and pages under it, username or full name in breadcrumb list isn't sanitized and triggered xss.
1. Access to the My Account Page ( /admin/myaccount )
2. Input the Full Name column : xss<script>alert('xss')</script>
3. Push the the Save button
4. Access to the My Account page ( /admin/myaccount ) or pages under it ( /admin/myaccount/addresses , /admin/myaccount/preferences , etc.) and it triggers xssIs GHSA-28h4-788g-rh42 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 craftcms/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.