Is statamic/cms 6.11 vulnerable?
Composer · 1 release from 6.11.0 to 6.11.0 · latest statamic/cms is 6.39.0 · checked 2 Nov 2026
Yes: 15 known advisories
Yes. statamic/cms 6.11.0, the last 6.11 release, is affected by 15 known security advisories (3 high, 11 medium, 1 low), including CVE-2026-64665, CVE-2026-49287, CVE-2026-41175. At least one has no fixed release yet.
Advisories affecting statamic/cms 6.11.0
Statamic: Stored Cross-Site Scripting in Automagic Form Notification Email Template
- Affected
- <5.74.3 · >=6.0.0 <6.24.2
- Fixed in
- 5.74.3, 6.24.2
Statamic: Missing file upload validation on frontend forms allows uploading disallowed file types
- Affected
- <5.74.3 · >=6.0.0 <6.24.2
- Fixed in
- 5.74.3, 6.24.2
Statamic: Missing authorization on navigation endpoint allows disclosure of restricted entries
- Affected
- <5.74.1 · >=6.0.0 <6.24.0
- Fixed in
- 5.74.1, 6.24.0
Statamic: Unsafe method invocation via Antlers template resolution allows data destruction
- Affected
- <5.74.1 · >=6.0.0 <6.24.0
- Fixed in
- 5.74.1, 6.24.0
Statamic: Account takeover via OAuth email matching without email-verification check
- Affected
- <5.74.1 · >=6.0.0 <6.24.0
- Fixed in
- 5.74.1, 6.24.0
Statamic: Missing authorization on Control Panel endpoint allows disclosure of user existence
- Affected
- <5.74.1 · >=6.0.0 <6.24.0
- Fixed in
- 5.74.1, 6.24.0
Statamic CMS exposes two-factor recovery codes through dynamic Antlers rendering
- Affected
- >=6.0.0-alpha.1 <=6.30.0
- Fixed in
- No fix released
Statamic CMS's incorrect authorization lets view-only users submit Live Preview content reserved for editors
- Affected
- <5.74.0 · >=6.0.0 <6.20.3
- Fixed in
- 5.74.0, 6.20.3
Statamic Vulnerable to CSV formula injection in form submission exports
- Affected
- >=6.0.0 <6.20.1 · <5.73.24
- Fixed in
- 5.73.24, 6.20.1
Statamic Vulnerable to Server-Side Request Forgery via Glide (DNS rebinding)
- Affected
- <5.73.24 · >=6.0.0 <6.20.1
- Fixed in
- 5.73.24, 6.20.1
Statamic CMS's unsafe method invocation via collection sorting allows data destruction
- Affected
- <5.73.23 · >=6.0.0 <6.20.0
- Fixed in
- 5.73.23, 6.20.0
Statamic CMS: Missing authorization on Control Panel fieldtype endpoints allows disclosure of restricted resources
- Affected
- <5.73.23 · >=6.0.0 <6.20.0
- Fixed in
- 5.73.23, 6.20.0
Statamic CMS: Server-Side Request Forgery via Glide
- Affected
- <5.73.22 · >=6.0.0-alpha.1 <6.18.1
- Fixed in
- 5.73.22, 6.18.1
Statamic CMS vulnerable to email enumeration via forgot password endpoint
- Affected
- <5.73.21 · >=6.0.0 <6.15.0
- Fixed in
- 5.73.21, 6.15.0
Statamic: Unsafe method invocation via query value resolution allows data destruction
- Affected
- <5.73.20 · >=6.0.0-alpha.1 <6.13.0
- Fixed in
- 5.73.20, 6.13.0
Which of your client projects are still on statamic/cms 6.11?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact statamic/cms version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other statamic/cms versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.