ghsa-28h4-788g-rh42
Vulnerability from github
5.1 (Medium) - CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L
Summary
Multiple Stored XSS can be triggered by the breadcrumb list and title fields with user input.
Details
- In the /admin/categories page, category title isn't sanitized and triggered xss.
- In the category edit page under the /admin/categories/, category title in breadcrumb list isn't sanitized and triggered xss.
- In the /admin/entries page, entry title isn't sanitized and triggered xss.
- In the entry edit page under the /admin/entries/, entry title in breadcrumb list isn't sanitized and triggered xss.
- 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 xss
2. 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 xss
3. 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 xss
4. 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 xss
5. 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 xss
{ "affected": [ { "package": { "ecosystem": "Packagist", "name": "craftcms/cms" }, "ranges": [ { "events": [ { "introduced": "5.0.0" }, { "fixed": "5.1.2" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-45406" ], "database_specific": { "cwe_ids": [ "CWE-79", "CWE-80" ], "github_reviewed": true, "github_reviewed_at": "2024-09-09T18:18:28Z", "nvd_published_at": "2024-09-09T17:15:13Z", "severity": "MODERATE" }, "details": "### Summary\nMultiple Stored XSS can be triggered by the breadcrumb list and title fields with user input.\n\n### Details\n1. In the **/admin/categories** page, category title isn\u0027t sanitized and triggered xss.\n2. In the category edit page under the **/admin/categories/**, category title in breadcrumb list isn\u0027t sanitized and triggered xss.\n3. In the **/admin/entries** page, entry title isn\u0027t sanitized and triggered xss.\n4. In the entry edit page under the **/admin/entries/**, entry title in breadcrumb list isn\u0027t sanitized and triggered xss.\n5. In the **/admin/myaccount** and pages under it, username or full name in breadcrumb list isn\u0027t sanitized and triggered xss.\n\n### Impact\nMalicious users can tamper with the control panel.\n\n### PoC\n#### 1. In the **/admin/categories** page, category title isn\u0027t sanitized and triggered xss.\n```\n1. Access to the Settings -\u003e Categories ( /admin/settings/categories )\n2. Create new category group\n3. Access to the Categories page ( /admin/categories/ )\n4. Push the New category button\n5. Input the Title column : xss\u003cscript\u003ealert(\u0027xss\u0027)\u003c/script\u003e\n6. Push the Create Category or Save button\n7. Access to the Categories page again and it triggers xss\n``` \n\n\n\n\n#### 2. In the category edit page under the **/admin/categories/**, category title in breadcrumb list isn\u0027t sanitized and triggered xss.\n```\n1. Access to the Settings -\u003e Categories ( /admin/settings/categories )\n2. Create new category group\n3. Access to the Categories page ( /admin/categories/ )\n4. Push the New category button\n5. Input the Title column : xss\u003cscript\u003ealert(\u0027xss\u0027)\u003c/script\u003e\n6. Push the Create Category or Save button\n7. Access to the Category edit page again and it triggers xss\n``` \n\n\n\n\n#### 3. In the **/admin/entries** page, entry title isn\u0027t sanitized and triggered xss.\n```\n1. Access to the Settings -\u003e Entry Types ( /admin/settings/entry-types )\n2. Create new entry type\n3. Access to the Settings -\u003e Sections ( /admin/settings/sections )\n4. Create new section\n5. Access to the Entries page ( /admin/entries )\n6. Push the New entry button\n7. Input the Title column : xss\u003cscript\u003ealert(\u0027xss\u0027)\u003c/script\u003e\n8. Push the Create entry or Save button\n9. Access to the Entries page again and it triggers xss\n``` \n\n\n\n\n#### 4. In the entry edit page under the **/admin/entries/**, entry title in breadcrumb list isn\u0027t sanitized and triggered xss.\n```\n1. Access to the Settings -\u003e Entry Types ( /admin/settings/entry-types )\n2. Create new entry type\n3. Access to the Settings -\u003e Sections ( /admin/settings/sections )\n4. Create new section\n5. Access to the Entries page ( /admin/entries )\n6. Push the New entry button\n7. Input the Title column : xss\u003cscript\u003ealert(\u0027xss\u0027)\u003c/script\u003e\n8. Push the Create entry or Save button\n9. Access to the Entriy edit page again and it triggers xss\n``` \n\n\n\n\n#### 5. In the **/admin/myaccount** and pages under it, username or full name in breadcrumb list isn\u0027t sanitized and triggered xss.\n```\n1. Access to the My Account Page ( /admin/myaccount )\n2. Input the Full Name column : xss\u003cscript\u003ealert(\u0027xss\u0027)\u003c/script\u003e\n3. Push the the Save button\n4. Access to the My Account page ( /admin/myaccount ) or pages under it ( /admin/myaccount/addresses , /admin/myaccount/preferences , etc.) and it triggers xss\n``` \n\n\n", "id": "GHSA-28h4-788g-rh42", "modified": "2024-09-09T19:30:14Z", "published": "2024-09-09T18:18:28Z", "references": [ { "type": "WEB", "url": "https://github.com/craftcms/cms/security/advisories/GHSA-28h4-788g-rh42" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-45406" }, { "type": "WEB", "url": "https://github.com/craftcms/cms/commit/b7348942f8131b3868ec6f46d615baae50151bb8" }, { "type": "PACKAGE", "url": "https://github.com/craftcms/cms" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L", "type": "CVSS_V3" }, { "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:L", "type": "CVSS_V4" } ], "summary": "Craft CMS vulnerable to stored XSS in breadcrumb list and title fields" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.