CVE-2026-46725 is an insecure deserialization vulnerability in the TYPO3 extension "Content Element Selector" (ceselector). The extension passes attacker-controlled cookie data directly to PHP's unserialize() function without safe processing or validation. An unauthenticated remote attacker can supply a crafted serialized payload in the cookie, triggering PHP Object Injection. In environments where a usable gadget chain is present, this can be leveraged to achieve remote code execution on the TYPO3 server. Exploitation is specifically dependent on the affected content element being configured with "Persistent Mode: Static" in the plugin settings.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit for an unauthenticated remote code execution vulnerability in the TYPO3 mmc/ceselector extension, identified in the repository as CVE-2026-46725. The repo has 3 files: two Python exploit variants (CVE-2026-46275.py and cve-2026-46275-v2.py) and a README. The filenames contain a likely typo ('46275') while the code and documentation consistently describe CVE-2026-46725. The exploit is not framework-based; it is a standalone Python tool using requests, argparse, threading/concurrent futures, and terminal UI helpers. Its core purpose is to exploit insecure deserialization in a T3_ceselector_* cookie. The documented attack flow is: request the target web root, extract the Set-Cookie value matching T3_ceselector_<id>, replace that cookie value with a URL-encoded PHP serialized Monolog gadget chain, then send another GET / request to trigger unserialize() and ultimately system(<cmd>). The exploit validates success by matching command output patterns in the HTTP response (README shows uid=... gid=... regex-style verification). Capabilities include: single-target exploitation, bulk scanning from a file, multithreaded execution, optional proxy support, configurable timeout, result saving, verbose mode, and an interactive shell mode that repeatedly sends commands after initial compromise. The payload is operational rather than merely demonstrative because it executes attacker-supplied commands, but it is still a standalone PoC-style script rather than a reusable framework module. Fingerprintable targets/endpoints are minimal and mostly target-supplied: the exploit interacts with the target root path '/', relies on the presence of a T3_ceselector_* cookie, and can route traffic through a user-specified proxy such as http://127.0.0.1:8080. The README also includes example target URLs and local file paths used in demonstration commands. No hardcoded C2, callback host, or external exfiltration endpoint is present. Overall, this repository is a real exploit implementation for web-based unauthenticated RCE against vulnerable TYPO3 ceselector deployments, contingent on the extension being active and configured with Persistent Mode: Static.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An insecure deserialization vulnerability affecting the TYPO3 ceselector extension.
A remote unauthenticated PHP Object Injection vulnerability in a TYPO3 extension caused by passing attacker-controlled cookie data to PHP unserialize(), which can lead to remote code execution when the content element is configured with "Persistent Mode: Static."
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.