CVE-2026-54243 is a medium-severity security vulnerability in statamic/cms (composer), affecting versions >= 6.0.0, < 6.20.1. It is fixed in 6.20.1, 5.73.24.
Impact Form submission values were not neutralized for spreadsheet formula characters when exported to CSV. A submission containing a value beginning with a formula trigger character (e.g. = , + , - , @ ) could be interpreted as a live formula when a Control Panel user opens the export in a spreadsheet application. Form submissions can come from unauthenticated front-end visitors, so the malicious value can be supplied by an anonymous user and is later triggered by an editor opening the export. Exploitation affects the spreadsheet application used to open the export, not the Statamic application or server; the data at risk is the form submission data the exporting user is already authorized to view. Patches This has been fixed in 5.73.24 and 6.20.1.
CVE-2026-54243 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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 (6.20.1, 5.73.24). Upgrading removes the vulnerable code path.
composer
statamic/cms (>= 6.0.0, < 6.20.1)statamic/cms (< 5.73.24)statamic/cms → 6.20.1 (composer)statamic/cms → 5.73.24 (composer)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 runtime-powered SCA identifies whether CVE-2026-54243 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-54243 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-54243 in your environment →Upgrade the following packages to resolve this vulnerability:
statamic/cms to 6.20.1 or laterstatamic/cms to 5.73.24 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-54243 is a medium-severity security vulnerability in statamic/cms (composer), affecting versions >= 6.0.0, < 6.20.1. It is fixed in 6.20.1, 5.73.24.
CVE-2026-54243 has a CVSS score of 6.1 (Medium). 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.
statamic/cms (composer) versions >= 6.0.0, < 6.20.1 is affected.
Yes. CVE-2026-54243 is fixed in 6.20.1, 5.73.24. Upgrade to this version or later.
Whether CVE-2026-54243 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
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.
statamic/cms to 6.20.1 or laterstatamic/cms to 5.73.24 or later