CVE-2021-44649 — django-cms
MEDIUMCVE-2021-44649 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in django-cms. 1 public exploit reference exists, so weaponization risk is real. A fix is available for django-cms — see the affected versions and patch details below.
Cross-site Scripting in django-cms
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2021-44649 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 383,485 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
django-cms🐍django-cms🐍django-cms🐍django-cmsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Django CMS 3.7.3 does not validate the plugin_type parameter while generating error messages for an invalid plugin type, resulting in a Cross Site Scripting (XSS) vulnerability. The vulnerability allows an attacker to execute arbitrary JavaScript code in the web browser of the affected user.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | django-cms | ≥ 3.7.0&&< 3.7.4 | 3.7.4pip install --upgrade 'django-cms==3.7.4' |
| 🐍PyPI | django-cms | ≥ 3.6.0&&< 3.6.1 | 3.6.1pip install --upgrade 'django-cms==3.6.1' |
| 🐍PyPI | django-cms | ≥ 3.5.0&&< 3.5.4 | 3.5.4pip install --upgrade 'django-cms==3.5.4' |
| 🐍PyPI | django-cms | ≥ 3.4.0&&< 3.4.7 | 3.4.7pip install --upgrade 'django-cms==3.4.7' |
Affected Products
django cmsdjango-cmsResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django-cms to 3.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-44649 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-2021-44649 in your dependencies?
Find it across PyPI, including transitive dependencies.