Unsafe Deserialization in mmc/ceselector (CVE-2026-46725)
Summary
Vulnerability in mmc/ceselector (CVE-2026-46725). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.0.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46725 has been found in mmc/ceselector.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mmc/ceselector to 3.0.3 or later.
If unsure, ask your IT team or search "mmc/ceselector CVE-2026-46725" on the vendor's site.
CVE-2026-46725 (mmc/ceselector) — CWE-502
Patched: 3.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in mmc/ceselector.
Check the vendor advisory for the affected versions of mmc/ceselector.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.0.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mmc/ceselector' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mmc/ceselector' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mmc/ceselectorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mmc/ceselector to 3.0.3ステージング環境で 3.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package bitbucket.org
- web typo3.org
- web github.com
- web github.com