Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61663 medium CVSS 4.3

Vulnerability in django-cms (CVE-2026-61663)

Summary

Vulnerability in django-cms (CVE-2026-61663). Risk of unauthorized operations or information disclosure. Exploitable via PageContent. Mitigation: upgrade to 5.0.9 or later.

Original description

The description as published by the source.

Summary

The django-cms frontend-editing structure endpoint

GET //admin/cms/placeholder/object//structure//

did not perform an object-level authorization check for non-PageContent objects. Any authenticated, active staff user could request the structure endpoint for a frontend-editable object (a model using PlaceholderRelationField) and read its placeholder/plugin structure, even without permission to change that object and without the cms.use_structure permission that the toolbar UI requires before offering structure mode.

PageContent objects were already protected (a page-view check added in GHSA/PR #8644); this advisory covers the remaining non-PageContent branch of the same view.

Severity

The issue is staff-gated and read-only, disclosing CMS structure metadata (placeholder slot names, plugin tree, plugin identifiers/labels, object existence) rather than write access or arbitrary field data.

Affected versions

  • django-cms >= 4.0.0, <= 5.0.x and 5.1.0a1
    (the vulnerable non-PageContent branch was introduced with the frontend-editing endpoints in 4.0)

Patched versions

  • django-cms TODO: 5.0.9

Preconditions

  • An authenticated, active staff account (is_staff=True).
  • The deployment exposes a non-PageContent model with django-cms placeholders / frontend editing (e.g. via PlaceholderRelationField).
  • The attacker can guess or enumerate the target content_type_id and object id.
  • The attacker needs no model/objec…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61663 has been found in django-cms.
Attackers can target a specific entry point like PageContent over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade django-cms to 5.0.9 or later.
If unsure, ask your IT team or search "django-cms CVE-2026-61663" on the vendor's site.

CVE-2026-61663 (django-cms) — CWE-639 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PageContent / PlaceholderRelationField / cms.use_structure / content_type_id
Patched: 5.0.9 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in django-cms. Attackers reach the vulnerable code path via PageContent.

📍 Affected scope

Check the vendor advisory for the affected versions of django-cms. Attack surface: PageContent / PlaceholderRelationField / cms.use_structure / content_type_id.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.0.9.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'django-cms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'django-cms' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で django-cms を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade django-cms to 5.0.9

    ステージング環境で 5.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip django-cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.9"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details