How severe is CVE-2026-46725?

No CVSS score has been assigned to CVE-2026-46725 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-46725?

CVE-2026-46725 affects the following packages: mmc/ceselector (Packagist), mmc/ceselector (Packagist), mmc/ceselector (Packagist), mmc/ceselector (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2026-46725?

Update mmc/ceselector to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46725 is resolved across your whole dependency graph.

How do I detect CVE-2026-46725 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mmc/ceselector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-46725 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is CVE-2026-46725 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-46725 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-46725?

CVE-2026-46725 has an EPSS (Exploit Prediction Scoring System) score of 1.9%, placing it in the 78th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-46725?

CVE-2026-46725 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2026-46725?

A Nuclei detection template exists for CVE-2026-46725, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2026-46725 published, and has it been updated?

CVE-2026-46725 was published on May 19, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2026-46725 — mmc/ceselector

CVE-2026-46725 is a Deserialization of Untrusted Data vulnerability in mmc/ceselector. A fix is available for mmc/ceselector — see the affected versions and patch details below.

TYPO3 Remote Code Execution in extension "Content Element Selector" (ceselector)

Published

May 19, 2026

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-46725.

EPSS Exploitation Probability

via FIRST.org ↗

1.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs78th percentile — riskier than 78% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘mmc/ceselector🐘mmc/ceselector🐘mmc/ceselector🐘mmc/ceselector

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mmc/ceselector`	≥ 6.0.0&&< 6.0.1	6.0.1`composer require mmc/ceselector:^6.0.1`
🐘Packagist	`mmc/ceselector`	≥ 5.0.0&&< 5.0.1	5.0.1`composer require mmc/ceselector:^5.0.1`
🐘Packagist	`mmc/ceselector`	≥ 4.0.0&&< 4.0.2	4.0.2`composer require mmc/ceselector:^4.0.2`
🐘Packagist	`mmc/ceselector`	all versions	3.0.3`composer require mmc/ceselector:^3.0.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mmc/ceselector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mmc/ceselector to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46725 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

How to detect CVE-2026-46725

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2026-46725 -u https://target

Template: TYPO3 ceselector Extension - Insecure Deserialization
Severity: critical
Impact: Remote unauthenticated attackers can execute arbitrary code on the TYPO3 server, leading to full system compromise.
Remediation: Update to the latest version of TYPO3 with the vulnerability fixed or apply patches that validate and sanitize unserialize input.

Template by ProjectDiscovery nuclei-templates (DhiyaneshDk), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-46725 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works