PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-54624 django-cms CVE debrief

CVE-2026-54624 is a medium-severity vulnerability in django CMS that allows staff accounts with CMS_PERMISSION to access restricted page structures, potentially exposing plugin descriptions. The issue is fixed in version 5.0.8. Defenders should review page view restrictions and CMS_PUBLIC_FOR settings, and upgrade to the fixed version. This vulnerability has a CVSS score of 6.5 and is considered medium-severity. The CVE record was published on 2026-08-20T19:16:55.583Z and has not been modified since then.

Vendor
django-cms
Product
Unknown
CVSS
MEDIUM 6.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-20
Original CVE updated
2026-09-09
Advisory published
2026-08-20
Advisory updated
2026-09-09

Who should care

Staff with CMS_PERMISSION enabled, developers and administrators of django CMS installations, and security teams should review and address this vulnerability. They should verify page view restrictions and CMS_PUBLIC_FOR settings, and upgrade to version 5.0.8 or later to address this vulnerability.

Why it matters

CVE-2026-54624 is a medium-severity vulnerability in django CMS that allows staff accounts with CMS_PERMISSION to access restricted page structures, potentially exposing plugin descriptions. Defenders should verify page view restrictions and CMS_PUBLIC_FOR settings, and upgrade to version 5.0.8 or later.

  • Potential exposure of plugin descriptions for restricted pages
  • Verification of page view restrictions and CMS_PUBLIC_FOR settings required
  • Upgrade to fixed version recommended for affected installations

Technical summary

CVE-2026-54624 is a medium-severity vulnerability in django CMS that allows staff accounts with CMS_PERMISSION to access restricted page structures. The issue is fixed in version 5.0.8. This vulnerability has a CVSS score of 6.5 and is considered medium-severity. The CVE record was published on 2026-08-20T19:16:55.583Z and has not been modified since then. Defenders should review page view restrictions and CMS_PUBLIC_FOR settings, and upgrade to the fixed version to address this vulnerability. The vulnerability allows staff accounts with CMS_PERMISSION to access restricted page structures, potentially exposing plugin descriptions.

Defensive priority

Medium priority for staff with CMS_PERMISSION enabled

Recommended defensive actions

  • Review and restrict CMS_PERMISSION for staff accounts
  • Verify page view restrictions and CMS_PUBLIC_FOR settings
  • Upgrade to django CMS version 5.0.8 or later
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

CVE Program and NVD records indicate a medium-severity issue in django CMS, allowing staff accounts with CMS_PERMISSION to access restricted page structures. The CVE record was published on 2026-08-20T19:16:55.583Z and has not been modified since then. Defenders should verify page view restrictions and CMS_PUBLIC_FOR settings, and upgrade to version 5.0.8 or later to address this vulnerability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-54624 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-54624

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-54624 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-54624

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.