Summary
TYPO3 Remote Code Execution in extension "Content Element Selector" (ceselector)
The TYPO3 "Content Element Selector" (ceselector) extension passes an attacker-controlled cookie directly to PHP's unserialize() without safely processing the input. A remote, unauthenticated attacker can supply a crafted serialized payload to trigger PHP Object Injection, leading to Remote Code Execution on the TYPO3 server. Exploitation requires the content element to be configured with Persistent Mode: Static in the plugin settings. This has been patched in version 3.0.3, 4.0.2, 5.0.1, and 6.0.1.
Impact
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
Affected versions
Security releases
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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
mmc/ceselector to 6.0.1 or later; mmc/ceselector to 5.0.1 or later; mmc/ceselector to 4.0.2 or later; mmc/ceselector to 3.0.3 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-46725? CVE-2026-46725 is a critical-severity insecure deserialization vulnerability in mmc/ceselector (composer), affecting versions >= 6.0.0, < 6.0.1. It is fixed in 6.0.1, 5.0.1, 4.0.2, 3.0.3. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- Which versions of mmc/ceselector are affected by CVE-2026-46725? mmc/ceselector (composer) versions >= 6.0.0, < 6.0.1 is affected.
- Is there a fix for CVE-2026-46725? Yes. CVE-2026-46725 is fixed in 6.0.1, 5.0.1, 4.0.2, 3.0.3. Upgrade to this version or later.
- Is CVE-2026-46725 exploitable, and should I be worried? Whether CVE-2026-46725 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-2026-46725 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-2026-46725?
- Upgrade
mmc/ceselectorto 6.0.1 or later - Upgrade
mmc/ceselectorto 5.0.1 or later - Upgrade
mmc/ceselectorto 4.0.2 or later - Upgrade
mmc/ceselectorto 3.0.3 or later
- Upgrade