CVE-2024-45406

CVE-2024-45406 is a medium-severity cross-site scripting (XSS) vulnerability in craftcms/cms (composer), affecting versions >= 5.0.0, < 5.1.2. It is fixed in 5.1.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Craft CMS vulnerable to stored XSS in breadcrumb list and title fields

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.

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



Impact

Malicious users can tamper with the control panel.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-45406 has a CVSS score of 5.5 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.1.2); upgrading removes the vulnerable code path.

Affected versions

craftcms/cms (>= 5.0.0, < 5.1.2)

Security releases

craftcms/cms → 5.1.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade craftcms/cms to 5.1.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2024-45406? CVE-2024-45406 is a medium-severity cross-site scripting (XSS) vulnerability in craftcms/cms (composer), affecting versions >= 5.0.0, < 5.1.2. It is fixed in 5.1.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
  2. How severe is CVE-2024-45406? CVE-2024-45406 has a CVSS score of 5.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of craftcms/cms are affected by CVE-2024-45406? craftcms/cms (composer) versions >= 5.0.0, < 5.1.2 is affected.
  4. Is there a fix for CVE-2024-45406? Yes. CVE-2024-45406 is fixed in 5.1.2. Upgrade to this version or later.
  5. Is CVE-2024-45406 exploitable, and should I be worried? Whether CVE-2024-45406 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2024-45406 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2024-45406? Upgrade craftcms/cms to 5.1.2 or later.

Other vulnerabilities in craftcms/cms

CVE-IDSeverityPackage summary
GHSA-86VW-X4WW-X467Highcraftcms/cms: Craft CMS: RCE via missing cleanseConfig in FieldsController::actionRenderCardPreviewGHSA-C43V-4CR8-6MVPLowcraftcms/cms: Craft CMS has authenticated path traversal in `assets/icon`, allowing local `.svg` file readCVE-2026-55794Highcraftcms/cms: Craft CMS: Potential authenticated Remote Code Execution via referrer redirectCVE-2026-55793Mediumcraftcms/cms: Craft CMS: Stored XSS via Structure entry title in table viewCVE-2026-55792Mediumcraftcms/cms: Craft CMS: Sensitive File Disclosure / Server-Side File Read

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo