CVE-2026-54623

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.8, the move_plugin endpoint in cms/admin/placeholderadmin.py accepts an attacker-controlled plugin_parent value without rejecting a plugin’s own identifier or a descendant identifier. A staff user with plugin-change permission under CMS_PERMISSION can create a parent_id cycle in the plugin tree. The _get_descendants_cte and _get_ancestors_cte queries in cms/models/pluginmodel.py have no cycle guard, so get_descendants() and later rendering, copy, or delete operations can recurse indefinitely or reach a database recursion limit, corrupting the tree and consuming request workers. This issue is fixed in versions 5.0.8.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 20, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Aug 20, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

5.0.8

Patch available: django-cms/django-cms 5.0.8

https://github.com/django-cms/django-cms/releases/tag/5.0.8
github_commit Patch Available

commit 7642a98ab317 (django-cms/django-cms)

Patch available: django-cms/django-cms 5.0.8 (contains commit 7642a98ab317)

https://github.com/django-cms/django-cms/commit/7642a98ab3170793c0b27b4125dd1f3d318b8a1c
github_pr Patch Available

fix: Enforce authorization on structure, move and clipboard endpoints (#8644)

Patch available: django-cms/django-cms 5.0.8 (PR #8645 merged 2026-06-05)

https://github.com/django-cms/django-cms/pull/8645
github Patch Available

Plugin move endpoint allows cyclic reparenting (DoS) · Advisory · django-cms/django-cms · GitHub

Affected: 5.0.8:

https://github.com/django-cms/django-cms/security/advisories/GHSA-8jj7-4v57-frf5

Vendor Advisories for CVE-2026-54623(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
django-cms2.0.1 ... 5.0.7 (140 versions)5.0.8—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 56× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:19 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 00:08 UTCEG score recompute
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 22:42 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescore
  7. 2026-09-16 09:41 UTCEG score recompute
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 07:29 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-13 17:14 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-12 16:32 UTCEG score recompute
  14. 2026-09-11 15:50 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-10 15:08 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 01:56 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-08 03:54 UTCEG score recompute
  21. 2026-09-07 16:01 UTCEPSS rescore
  22. 2026-09-07 01:23 UTCEG score recompute
  23. 2026-09-06 13:47 UTCEPSS rescore
  24. 2026-09-06 00:40 UTCEG score recompute
  25. 2026-09-04 23:51 UTCEG score recompute
Show 31 more
  1. 2026-09-04 10:41 UTCEG score recompute
  2. 2026-09-04 05:06 UTCEPSS rescore
  3. 2026-09-02 21:09 UTCEG score recompute
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 19:54 UTCEG score recompute
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 07:26 UTCEG score recompute
  8. 2026-09-01 04:40 UTCEPSS rescore
  9. 2026-08-31 02:59 UTCEG score recompute
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 02:14 UTCEG score recompute
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-29 01:28 UTCEG score recompute
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-28 00:45 UTCEG score recompute
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 23:53 UTCEG score recompute
  18. 2026-08-26 14:46 UTCEPSS rescore
  19. 2026-08-25 23:10 UTCEG score recompute
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 22:08 UTCEG score recompute
  22. 2026-08-24 09:46 UTCEG score recompute
  23. 2026-08-23 09:03 UTCEG score recompute
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 08:21 UTCEG score recompute
  26. 2026-08-21 23:49 UTCEPSS rescore
  27. 2026-08-20 19:18 UTCEG score recompute
  28. 2026-08-20 18:52 UTCEG score recompute
  29. 2026-08-20 18:17 UTCEG score recompute
  30. 2026-08-20 18:07 UTCEG score recompute
  31. 2026-08-20 18:06 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54623?
CVE-2026-54623 is a high vulnerability published on August 20, 2026. django CMS is an easy-to-use and developer-friendly enterprise content management system powered by Django. Prior to 5.0.8, the moveplugin endpoint in cms/admin/placeholderadmin.py accepts an attacker-controlled pluginparent value without rejecting a plugin’s own identifier or a descendant…
When was CVE-2026-54623 disclosed?
CVE-2026-54623 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54623 actively exploited?
CVE-2026-54623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.9% of all scored CVEs.
What is the CVSS score of CVE-2026-54623?
CVE-2026-54623 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-54623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54623, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54623

Explore →

Is Your Infrastructure Affected by CVE-2026-54623?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs