CVE-2024-41709 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in backdrop/backdrop. A fix is available for backdrop/backdrop — see the affected versions and patch details below.
Backdrop CMS does not sufficiently sanitize field labels before they are displayed in certain places
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-41709.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
backdrop/backdrop🐘backdrop/backdropReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Backdrop CMS before 1.27.3 and 1.28.x before 1.28.2 does not sufficiently sanitize field labels before they are displayed in certain places. This vulnerability is mitigated by the fact that an attacker must have a role with the "administer fields" permission.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | backdrop/backdrop | all versions | 1.27.3composer require backdrop/backdrop:^1.27.3 |
| 🐘Packagist | backdrop/backdrop | ≥ 1.28.0&&< 1.28.2 | 1.28.2composer require backdrop/backdrop:^1.28.2 |
Affected Products
backdropbackdropcmsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for backdrop/backdrop, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update backdrop/backdrop to 1.27.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41709 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-41709 in your dependencies?
Find it across Packagist, including transitive dependencies.