statamic/cms

CVE-2023-48217

CVE-2023-48217 is a high-severity code injection vulnerability in statamic/cms (composer), affecting versions >= 4.0.0, < 4.34.0. It is fixed in 4.34.0, 3.4.14.

Key facts
CVSS score
8.8
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
statamic/cms
Fixed in
4.34.0, 3.4.14
Disclosed
2023

Summary

Impact Similar to another advisory, certain additional PHP files crafted to look like images may be uploaded regardless of mime type validation rules. This affects front-end forms using the "Forms" feature, and asset upload fields in the control panel. Patches It has been patched in 3.4.14 and 4.34.0.

Impact

What is code injection?

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

Severity and exposure

CVE-2023-48217 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (4.34.0, 3.4.14). Upgrading removes the vulnerable code path.

Affected versions

composer

  • statamic/cms (>= 4.0.0, < 4.34.0)
  • statamic/cms (< 3.4.14)

Security releases

  • statamic/cms → 4.34.0 (composer)
  • statamic/cms → 3.4.14 (composer)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's Application Detection and Response identifies whether CVE-2023-48217 is reachable in your applications. Explore runtime application protection for your team.

See if CVE-2023-48217 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2023-48217 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade statamic/cms to 4.34.0 or later
  • Upgrade statamic/cms to 3.4.14 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2023-48217

What is CVE-2023-48217?

CVE-2023-48217 is a high-severity code injection vulnerability in statamic/cms (composer), affecting versions >= 4.0.0, < 4.34.0. It is fixed in 4.34.0, 3.4.14. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2023-48217?

CVE-2023-48217 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of statamic/cms are affected by CVE-2023-48217?

statamic/cms (composer) versions >= 4.0.0, < 4.34.0 is affected.

Is there a fix for CVE-2023-48217?

Yes. CVE-2023-48217 is fixed in 4.34.0, 3.4.14. Upgrade to this version or later.

Is CVE-2023-48217 exploitable, and should I be worried?

Whether CVE-2023-48217 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2023-48217 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-48217?
  • Upgrade statamic/cms to 4.34.0 or later
  • Upgrade statamic/cms to 3.4.14 or later

Stop the waste.
Protect your environment with Kodem.