Vulnerability in statamic/cms (CVE-2026-41175)
Summary
Vulnerability in statamic/cms (CVE-2026-41175). Data can be tampered with by attackers. Mitigation: upgrade to 5.73.20 or later.
Original description
The description as published by the source.
Impact
Manipulating query parameters on Control Panel and REST API endpoints, or arguments in GraphQL queries, could result in the loss of content, assets, and user accounts.
The Control Panel requires authentication with minimal permissions in order to exploit. e.g. "view entries" permission to delete entries, or "view users" permission to delete users, etc.
The REST and GraphQL API exploits do not require any permissions, however neither are enabled by default. In order to be exploited, they would need to be explicitly enabled with no authentication configured, and the specific resources enabled too.
Sites that enable the REST or GraphQL API without authentication should treat patching as critical priority.
Patches
This has been fixed in 5.73.20 and 6.13.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-41175 has been found in statamic/cms.
Data can be tampered with by attackers.
What to do: upgrade statamic/cms to 5.73.20 or later.
If unsure, ask your IT team or search "statamic/cms CVE-2026-41175" on the vendor's site.
CVE-2026-41175 (statamic/cms) — CWE-470
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.73.20 — 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.
A vulnerability (CWE-470) exists in statamic/cms.
Check the vendor advisory for the affected versions of statamic/cms.
Severity: ?. Data can be tampered with by attackers.
Update to 5.73.20.
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.73.20ステージング環境で 5.73.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com