VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

django-cms: vulnerability history, versions and safety

django-cms is a package in the PyPI ecosystem. Vulert records 20 vulnerabilities for it across 120 releases, from Aug 2017 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
20 vulnerabilities recorded H2 M8 U10
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
14 in the last 12 months

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all django-cms vulnerabilities

Vulert verdict on django-cms 5.1.3 i

Updated on 23 Oct 2026

Action needed: 5.1.3 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 67/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 5.1.3 — affected i
  • Vulnerabilities on record 20 over 9 years · 14 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 182 packages i
  • Stars 10,675 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for django-cms, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.0.13 24 Sep 2026 U1 BSD-3-Clause Yes Details →
5.1.3 23 Sep 2026 U1 BSD-3-Clause Yes Details →
5.0.12 23 Sep 2026 U1 BSD-3-Clause Yes Details →
5.0.11 27 Aug 2026 U1 BSD-3-Clause Yes Details →
5.1.2 27 Aug 2026 U1 BSD-3-Clause Yes Details →
5.1.1 06 Aug 2026 U1 BSD-3-Clause Yes Details →
5.0.10 06 Aug 2026 U1 BSD-3-Clause Yes Details →
5.1.0 13 Jul 2026 U1 BSD-3-Clause Yes Details →
5.0.9 10 Jul 2026 U1 BSD-3-Clause Yes Details →
5.0.8 10 Jun 2026 M3 U3 BSD-3-Clause Yes Details →
5.0.7 08 May 2026 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.11 05 May 2026 H1 M5 U6 BSD-3-Clause Yes Details →
3.11.11 05 May 2026 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.10 04 Mar 2026 H1 M5 U6 BSD-3-Clause Yes Details →
5.0.6 22 Feb 2026 H1 M5 U6 BSD-3-Clause Yes Details →
5.1.0a1 14 Feb 2026 U1 BSD-3-Clause Yes Details →
5.0.5 12 Nov 2025 H1 M5 U6 BSD-3-Clause Yes Details →
5.0.4 03 Oct 2025 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.9 30 Sep 2025 H1 M5 U6 BSD-3-Clause Yes Details →
5.1.0.dev1 28 Sep 2025 U1 BSD-3-Clause Yes Details →
5.0.3 17 Sep 2025 H1 M5 U6 BSD-3-Clause Yes Details →
5.0.2 17 Jul 2025 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.7 11 Jul 2025 H1 M5 U6 BSD-3-Clause Yes Details →
5.0.1 21 May 2025 H1 M5 U6 BSD-3-Clause Yes Details →
5.0.0 12 May 2025 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.6 22 Apr 2025 H1 M5 U6 BSD-3-Clause Yes Details →
3.11.10 05 Apr 2025 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.5 04 Apr 2025 H1 M5 U6 BSD-3-Clause Yes Details →
5.0.0a1 03 Mar 2025 H1 M5 U6 BSD-3-Clause Yes Details →
4.1.4 13 Nov 2024 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.9 13 Nov 2024 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.3 08 Oct 2024 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.8 11 Sep 2024 H1 M6 U7 BSD-3-Clause Yes Details →
3.11.7 09 Sep 2024 H1 M6 U7 BSD-3-Clause Yes Details →
4.1.2 18 Jul 2024 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.6 18 May 2024 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.1 01 May 2024 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.5 09 Feb 2024 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.0 31 Dec 2023 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.0rc5 12 Dec 2023 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.4 08 Sep 2023 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.0rc4 30 Aug 2023 H1 M5 U7 BSD-3-Clause Yes Details →
3.8.2 21 Jun 2023 H1 M5 U7 BSD-3-Clause Yes Details →
3.8.1 18 Jun 2023 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.0rc3 16 May 2023 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.0rc2 25 Apr 2023 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.3 25 Apr 2023 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.2 18 Apr 2023 H1 M5 U7 BSD-3-Clause Yes Details →
4.1.0rc1 31 Dec 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.1 13 Dec 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.1rc1 14 Nov 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.11.0 02 Aug 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.10.1 27 Jun 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.10.1rc1 01 Jun 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.10.0 26 Mar 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.10.0rc2 05 Mar 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.10.0rc1 01 Feb 2022 H1 M5 U7 BSD-3-Clause Yes Details →
3.9.0 29 Jun 2021 H1 M5 U7 BSD-3-Clause Yes Details →
3.9.0rc3 20 Jun 2021 H1 M5 U7 BSD-3-Clause Yes Details →
3.9.0rc2 21 May 2021 H1 M5 U7 BSD-3-Clause Yes Details →
3.9.0rc1 19 May 2021 H1 M5 U7 BSD-3-Clause Yes Details →
3.8.0 28 Oct 2020 H1 M5 U7 BSD-3-Clause Yes Details →
3.8.0rc1 17 Sep 2020 H1 M5 U7 BSD-3-Clause Yes Details →
3.7.4 21 Jul 2020 H1 M5 U7 non-standard Yes Details →
3.6.1 21 Jul 2020 H1 M5 U7 non-standard Yes Details →
3.5.4 21 Jul 2020 H1 M5 U7 non-standard Yes Details →
3.4.7 21 Jul 2020 H1 M5 U7 non-standard Yes Details →
3.7.3 27 May 2020 H1 M6 U8 non-standard Yes Details →
3.7.2 22 Apr 2020 H1 M6 U8 non-standard Yes Details →
3.7.1 26 Nov 2019 H1 M6 U8 non-standard Yes Details →
3.7.0 25 Sep 2019 H1 M6 U8 non-standard Yes Details →
3.7.0rc2 27 Aug 2019 H1 M5 U7 non-standard Yes Details →
3.7.0rc1 14 Aug 2019 H1 M5 U7 non-standard Yes Details →
3.6.0 29 Jan 2019 H1 M5 U8 non-standard Yes Details →
3.6.0rc3 24 Jan 2019 H1 M5 U7 non-standard Yes Details →
3.6.0rc1 22 Jan 2019 H1 M5 U7 non-standard Yes Details →
3.5.3 20 Nov 2018 H1 M5 U8 non-standard Yes Details →
3.5.2 11 Apr 2018 H1 M5 U8 non-standard Yes Details →
3.4.6 26 Mar 2018 H1 M5 U8 non-standard Yes Details →
3.5.1 05 Mar 2018 H1 M5 U8 non-standard Yes Details →
3.5.0 31 Jan 2018 H1 M5 U8 non-standard Yes Details →
3.4.5 12 Oct 2017 H1 M5 U8 non-standard Yes Details →
3.4.4 15 Jun 2017 H1 M5 U8 non-standard Yes Details →
3.4.3 25 Apr 2017 H1 M5 U8 non-standard Yes Details →
3.3.4 25 Apr 2017 H1 M5 U7 non-standard Yes Details →
3.4.2 23 Jan 2017 H1 M5 U8 non-standard Yes Details →
3.4.1 04 Oct 2016 H1 M5 U8 non-standard Yes Details →
3.3.3 04 Oct 2016 H1 M5 U7 non-standard Yes Details →
3.4.0 14 Sep 2016 H1 M5 U8 non-standard Yes Details →
3.3.2 11 Aug 2016 H1 M5 U7 non-standard Yes Details →
3.3.1 13 Jul 2016 H1 M5 U7 non-standard Yes Details →
3.3.0 26 May 2016 H1 M5 U7 non-standard Yes Details →
3.3.0rc4 25 May 2016 H1 M5 U7 non-standard Yes Details →
3.3.0rc3 24 May 2016 H1 M5 U7 non-standard Yes Details →
3.3.0rc2 20 May 2016 H1 M5 U7 non-standard Yes Details →
3.0.18 27 Apr 2016 H1 M5 U7 non-standard Yes Details →
3.1.7 27 Apr 2016 H1 M5 U7 non-standard Yes Details →
3.2.5 27 Apr 2016 H1 M5 U7 non-standard Yes Details →
3.2.4.0 26 Apr 2016 H1 M5 U7 non-standard Yes Details →
3.1.6 26 Apr 2016 H1 M5 U7 non-standard Yes Details →
3.0.17 26 Apr 2016 H1 M5 U7 — Yes Details →
3.2.3 09 Mar 2016 H1 M5 U7 — Yes Details →
3.2.2 03 Mar 2016 H1 M5 U7 — Yes Details →
3.1.5 29 Jan 2016 H1 M5 U7 — Yes Details →
3.2.1 29 Jan 2016 H1 M5 U7 — Yes Details →
3.0.16 24 Nov 2015 H1 M5 U7 — Yes Details →
3.1.4 24 Nov 2015 H1 M5 U7 — Yes Details →
3.2.0 24 Nov 2015 H1 M5 U7 — Yes Details →
3.1.3 01 Sep 2015 H1 M5 U7 — Yes Details →
3.0.15 01 Sep 2015 H1 M5 U7 — Yes Details →
3.1.2 03 Jul 2015 H1 M5 U7 — Yes Details →
3.1.1 27 Jun 2015 H1 M5 U7 — Yes Details →
3.0.14 27 Jun 2015 H1 M5 U7 — Yes Details →
3.1.0 20 Apr 2015 H1 M5 U8 — Yes Details →
3.1.0rc2 18 Apr 2015 H1 M5 U7 — Yes Details →
3.0.13 15 Apr 2015 H2 M5 U8 — Yes Details →
3.1.0rc1 11 Apr 2015 H1 M5 U7 — Yes Details →
3.1.0b1 26 Mar 2015 H1 M5 U7 — Yes Details →
3.0.12 05 Mar 2015 H2 M5 U8 — Yes Details →
3.0.11 04 Mar 2015 H2 M5 U8 — Yes Details →

The newest 120 of 152 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2017 1
  • 2022 3
  • 2024 2
  • 2026 14

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 14 of the 20 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for django-cms

The 5 most severe of 20 vulnerabilities recorded for this package

Search all 20 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2015-5081: django-cms CSRF Vulnerability 8.8 high 3.0.14 17 May 2022
CVE-2026-54623: django CMS Plugin Move Endpoint Allows Cyclic Reparenting (DoS) 7.1 high 5.0.8 10 Sep 2026
CVE-2026-54623: django CMS Plugin Move Endpoint Allows Cyclic Reparenting (DoS) 7.1 high 5.0.8 24 Aug 2026
CVE-2026-54622: django CMS Clipboard Copy IDOR Vulnerability Exposes Unauthorized Plugin Content 6.5 medium 5.0.8 10 Sep 2026
CVE-2026-54624: django CMS Structure Endpoint Bypass of Page-View Permission 6.5 medium 5.0.8 10 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About django-cms

Is django-cms safe to use?

Vulert records 20 vulnerabilities for django-cms in PyPI: 0 critical, 2 high, 8 medium and 0 low, plus 10 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is django-cms's Vulert package health score?

Vulert scores django-cms 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of django-cms affected?

Yes. 5.1.3, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of django-cms should I use?

5.1.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does django-cms have?

20 vulnerabilities are recorded for django-cms in the PyPI ecosystem: 0 critical, 2 high, 8 medium and 0 low, plus 10 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new django-cms vulnerabilities disclosed?

14 vulnerabilities were recorded for django-cms in the last 12 months, and the oldest entry in this database dates to 18 Aug 2017. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of django-cms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor django-cms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the django-cms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.