Ckeditor 4 · Version Status
Ckeditor 4 End of Life Date
Ckeditor 4 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Ckeditor 4 is past end of life. This version no longer receives security patches. 1044 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 30, 2023
1044 days past EOL
Latest Release
4.25.1
LTS release
Release Date
Nov 23, 2012
Ckeditor 4 series
| Version | Latest | EOL Date | Status |
|---|
| → 4 LTS |
4.25.1 |
Jun 30, 2023 |
EOL |
| 5 |
47.6.1 |
EOL |
Active |
What does Ckeditor 4 end of life mean?
When Ckeditor 4 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Ckeditor 4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Ckeditor 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Ckeditor 4 reach end of life?
Ckeditor 4 reached end of life on June 30, 2023. This version is no longer receiving security patches.
Is Ckeditor 4 still supported?
No. Ckeditor 4 reached end of life on June 30, 2023 and is no longer receiving security patches.
What should I upgrade to from Ckeditor 4?
The recommended upgrade from Ckeditor 4 is
Ckeditor 5 — the latest actively supported version. Check the
Ckeditor full timeline for all supported versions.
What are the security risks of running Ckeditor 4 past EOL?
When Ckeditor 4 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Ckeditor should migrate immediately or implement compensating controls.