Authorization Flaw in statamic/cms (CVE-2026-54244)
Summary
Vulnerability in statamic/cms (CVE-2026-54244). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.74.0 or later.
Original description
The description as published by the source.
Impact
The Live Preview endpoint for existing entries and terms only checked view authorization, but it accepts and renders caller-supplied field values. A Control Panel user with view but not edit permission could therefore submit content they were not authorized to author and generate a shareable Live Preview URL rendering it.
Patches
This has been fixed in 5.74.0 and 6.20.3.
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-54244 has been found in statamic/cms.
Risk of unauthorized operations or information disclosure. CVSS score: 3.5/10.
What to do: upgrade statamic/cms to 5.74.0 or later.
If unsure, ask your IT team or search "statamic/cms CVE-2026-54244" on the vendor's site.
CVE-2026-54244 (statamic/cms) — CWE-863 / CVSS v3 3.5
Attack vector: remote (network-reachable)
Patched: 5.74.0 — 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.
Incorrect authorization (CWE-863) exists in statamic/cms.
Check the vendor advisory for the affected versions of statamic/cms.
Severity: Low (CVSS 3.5/10). Risk of unauthorized operations or information disclosure.
Update to 5.74.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'statamic/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
-
1Identify exposure identify
grep -r 'statamic/cms' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
statamic/cmsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade statamic/cms to 5.74.0ステージング環境で 5.74.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web security-advisories@github.com