← Back
CVE-2026-63003
medium
CVSS 6.5
Vulnerability in django-cms (CVE-2026-63003)
Summary
vulnerability in django-cms (CVE-2026-63003). Confidential information can be exposed externally. Exploitable via `POST /admin/cms/pagecontent/`. Mitigation: upgrade to `5.0.9` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-63003** has been found in django-cms.
Attackers can target a specific entry point like `POST /admin/cms/pagecontent/` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/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-63003" on the vendor's site.
CVE-2026-63003 (django-cms) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /admin/cms/pagecontent/ / `PageAdmin.has_add_permission` / `AddPageForm.__init__` / `source`
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 `POST /admin/cms/pagecontent/` without authentication.
📍 Affected scope
django-cms — . Attack surface: POST /admin/cms/pagecontent/ / `PageAdmin.has_add_permission` / `AddPageForm.__init__` / `source`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 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 `POST /admin/cms/pagecontent/` requests with malformed payloads or SQL meta-characters. Run `grep -r 'django-cms' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django-cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `django-cms` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /admin/cms/pagecontent/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /admin/cms/pagecontent/` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade django-cms to 5.0.9ステージング環境で 5.0.9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /admin/cms/pagecontent/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
django-cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.9"}]}]