Craft CMS vulnerable to stored XSS in breadcrumb list and title fields
CVE-2024-45406GHSA-28h4-788g-rh42
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (craftcms/cms 5.1.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist craftcms/cms
- Affected
- >= 5.0.0, < 5.1.2
- Fixed in
- 5.1.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-28h4-788g-rh42 lists affected ranges: Packagist craftcms/cms >=5.0.0 <5.1.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.1 · 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 · score source
- EPSS
- CVE-2024-45406: 0.35% estimated exploitation activity in the next 30 days; percentile 29.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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. 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.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-28h4-788g-rh42
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-45406 Advisory: Craft CMS vulnerable to stored XSS in breadcrumb list and title fields IDs: CVE-2024-45406, GHSA-28h4-788g-rh42 Record: https://patchnext.com/advisories/cve-2024-45406 (revision 1, source checked 26 Oct 2026, 14:26 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: craftcms/cms 5.1.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist craftcms/cms: affected >= 5.0.0, < 5.1.2; fixed in 5.1.2 ## Suggested inspection (read-only) - Packagist craftcms/cms: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on craftcms/cms. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-28h4-788g-rh42 (GitHub-reviewed advisory GHSA-28h4-788g-rh42 lists affected ranges: Packagist craftcms/cms >=5.0.0 <5.1.2) Commands are suggestions: review each one before running it.
Loading voting…