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.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
40th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 pull request 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 advisoryMentions a patch (unverified)

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 rangeFix by version rangeDependents
django-cms2.0.1 ... 5.0.7 (140 versions)
  • every version up to 5.0.8: fixed in 5.0.8
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 54× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-11 19:39 UTCEG score recompute
  2. 2026-10-11 16:54 UTCEG score recompute
  3. 2026-10-11 14:17 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-09 08:27 UTCEG score recompute
  8. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-08 05:19 UTCEG score recompute
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-06 16:53 UTCEG score recompute
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-06 03:21 UTCEG score recompute
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-05 09:29 UTCEG score recompute
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-03 16:47 UTCEG score recompute
  18. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-02 22:13 UTCEG score recompute
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-01 21:29 UTCEG score recompute
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-09-30 20:34 UTCEG score recompute
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-09-30 08:13 UTCEG score recompute
Show 72 more
  1. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-09-28 21:38 UTCEG score recompute
  3. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-09-27 15:57 UTCEG score recompute
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-09-27 03:00 UTCEG score recompute
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-09-25 01:07 UTCEG score recompute
  9. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-09-24 00:24 UTCEG score recompute
  11. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  12. 2026-09-22 23:43 UTCEG score recompute
  13. 2026-09-21 22:51 UTCEG score recompute
  14. 2026-09-20 22:08 UTCEG score recompute
  15. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  16. 2026-09-19 21:25 UTCEG score recompute
  17. 2026-09-18 20:19 UTCEG score recompute
  18. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  19. 2026-09-18 00:08 UTCEG score recompute
  20. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-09-16 22:42 UTCEG score recompute
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-09-16 09:41 UTCEG score recompute
  24. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  25. 2026-09-15 07:29 UTCEG score recompute
  26. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  27. 2026-09-13 17:14 UTCEG score recompute
  28. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  29. 2026-09-12 16:32 UTCEG score recompute
  30. 2026-09-11 15:50 UTCEG score recompute
  31. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  32. 2026-09-10 15:08 UTCEG score recompute
  33. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  34. 2026-09-09 01:56 UTCEG score recompute
  35. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  36. 2026-09-08 03:54 UTCEG score recompute
  37. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  38. 2026-09-07 01:23 UTCEG score recompute
  39. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  40. 2026-09-06 00:40 UTCEG score recompute
  41. 2026-09-04 23:51 UTCEG score recompute
  42. 2026-09-04 10:41 UTCEG score recompute
  43. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  44. 2026-09-02 21:09 UTCEG score recompute
  45. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  46. 2026-09-01 19:54 UTCEG score recompute
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  48. 2026-09-01 07:26 UTCEG score recompute
  49. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  50. 2026-08-31 02:59 UTCEG score recompute
  51. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  52. 2026-08-30 02:14 UTCEG score recompute
  53. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  54. 2026-08-29 01:28 UTCEG score recompute
  55. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  56. 2026-08-28 00:45 UTCEG score recompute
  57. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  58. 2026-08-26 23:53 UTCEG score recompute
  59. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  60. 2026-08-25 23:10 UTCEG score recompute
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  62. 2026-08-24 22:08 UTCEG score recompute
  63. 2026-08-24 09:46 UTCEG score recompute
  64. 2026-08-23 09:03 UTCEG score recompute
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  66. 2026-08-22 08:21 UTCEG score recompute
  67. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  68. 2026-08-20 19:18 UTCEG score recompute
  69. 2026-08-20 18:52 UTCEG score recompute
  70. 2026-08-20 18:17 UTCEG score recompute
  71. 2026-08-20 18:07 UTCEG score recomputeFirst assessed: 7.1 HIGH
  72. 2026-08-20 18:06 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54623?
CVE-2026-54623 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-54623 published?
The CVE record for CVE-2026-54623 was published on August 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-54623 actively exploited?
CVE-2026-54623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54623?
CVE-2026-54623 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54623?
A fix for CVE-2026-54623 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54623 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs