← Back
CVE-2026-54625
medium
CVSS 4.8
Vulnerability in django-cms (CVE-2026-54625)
Summary
vulnerability in django-cms (CVE-2026-54625). Risk of unauthorized operations or information disclosure. Exploitable via ``Vary``. Mitigation: upgrade to `5.0.8` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54625** has been found in django-cms.
Attackers can target a specific entry point like ``Vary`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.8/10.
What to do: upgrade django-cms to **5.0.8** or later.
If unsure, ask your IT team or search "django-cms CVE-2026-54625" on the vendor's site.
CVE-2026-54625 (django-cms) — CWE-349 / CVSS v3 4.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Vary` / `_page_cache_key` / `set_page_cache` / `get_page_cache`
Patched: `5.0.8` — apply immediately
Workaround: Disable `CMS_PAGE_CACHE`, or avoid plugins that rely on `get_vary_cache_on()`, until upgraded.
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-349) exists in django-cms. Attackers reach the vulnerable code path via ``Vary`` without authentication.
📍 Affected scope
django-cms — . Attack surface: `Vary` / `_page_cache_key` / `set_page_cache` / `get_page_cache`.
🔥 Severity
Severity: Medium (CVSS 4.8/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.0.8**.
🛡️ Workaround
Workaround: Disable `CMS_PAGE_CACHE`, or avoid plugins that rely on `get_vary_cache_on()`, until upgraded.
🔍 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 (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 し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Disable `CMS_PAGE_CACHE`, or avoid plugins that rely on `get_vary_cache_on()`, until upgraded.パッチが適用されるまでの応急処置として、Disable `CMS_PAGE_CACHE`, or avoid plugins that rely on `get_vary_cache_on()`, until upgraded. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade django-cms to 5.0.8ステージング環境で 5.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
django-cms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.8"}]}]
References
- web https://github.com/django-cms/django-cms/commit/8758714b865ffa79c6bcd0e5c503958ea48885aa
- web https://github.com/django-cms/django-cms/commit/d5dc1efa18d157445491c4b12c2dd1efd56f439f
- web https://github.com/django-cms/django-cms/pull/8646
- web https://github.com/django-cms/django-cms/pull/8647
- web https://github.com/django-cms/django-cms/releases/tag/5.0.8
- web https://github.com/django-cms/django-cms/releases/tag/5.1.0
- web https://github.com/django-cms/django-cms/security/advisories/GHSA-fwjf-m4qw-9f2x
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54625
- web https://github.com/advisories/GHSA-fwjf-m4qw-9f2x