CKEditor 4 · Version Status
CKEditor 4 End of Life Date
CKEditor 4 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
CKEditor 4 is past end of life. Standard support ended June 30, 2023. Patches continue until December 1, 2028 only under CKEditor 4 LTS, a paid programme — if you are not covered by it, this version is unpatched today.
EOL Date
Jun 30, 2023
1226 days past EOL
Latest Release
4.25.2
LTS release
Release Date
Nov 23, 2012
CKEditor 4 series
Extended Support
Dec 1, 2028
CKEditor 4 LTS · paid
Where these dates come from
End of lifeJun 30, 2023endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees End of extended supportDec 1, 2028endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseNov 23, 2012endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
CKEditor 4 was released on November 23, 2012 and support ended on June 30, 2023 — a supported lifespan of 10 years and 7 months. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. Its most recent release is 4.25.2, published July 10, 2026. Standard support ended 3 years and 4 months ago. Security fixes now come only through extended support, published to December 1, 2028; without it this version is unpatched.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended CKEditor 4 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| → 4 LTS |
4.25.2 |
Jun 30, 2023 |
EOL |
| 5 |
49.0.0 |
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 except under CKEditor 4 LTS (paid), until Dec 1, 2028. 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running CKEditor 4 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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. Security patches continue only under CKEditor 4 LTS (paid), until December 1, 2028; without it this version receives none.
Is CKEditor 4 still supported?
Not in standard support. CKEditor 4 reached end of life on June 30, 2023; security patches continue only under CKEditor 4 LTS (paid) until December 1, 2028.
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?
Since CKEditor 4 reached end of life, the maintainers no longer issue security patches outside CKEditor 4 LTS. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL CKEditor should migrate immediately or implement compensating controls.