CKEditor 4 shows a 'this version is not secure' notification
This CKEditor 4.22.1 version is not secure. Consider upgrading to the latest oneShort answer
CKEditor 4.22 and older run a version check that shows this notification, because those releases no longer get security fixes. The real fix is to move to CKEditor 4 LTS (4.25.0-lts or newer, under the Extended Support Model) or to CKEditor 5. Setting config.versionCheck to false only hides the message.
Fix it fast
1Find out which cause you have
Find out which CKEditor version is actually loaded. The browser console tells you, whatever package.json says.
// browser console on the page with the editor CKEDITOR.version2Match what you see, then jump to its fix
What does the error look like?
This CKEditor 4.22.1 version is not secure. Consider upgrading to the latest oneCKEditor notification bar at the top of the editor
Cause 1 of 2
You are running 4.22.x or older, which gets no security fixes
1Check
The version check was added in 4.22.0 and is on by default in 4.22 and below. The release notes for 4.24.0-lts and 4.25.0-lts state that all versions below the new release can no longer be considered secure.
npm ls | grep -i ckeditor2Fix
Choose one path. Either get the Extended Support Model and install CKEditor 4 LTS 4.25.0-lts or newer (activate the key as CKEditor's LTS key activation guide describes), or migrate to CKEditor 5. Within CKEditor 4, versions 4.23.0 and above are the LTS line.
# check which LTS build you are entitled to, then load that build
# (the notification names the version it recommends)
npm ls ckeditor43Verify
Reload the page and read the version, then check that the notification is gone.
CKEDITOR.versionConfirmed by ckeditor.com
Cause 2 of 2
The notification is a feature you can switch off, with a cost
1Check
config.versionCheck exists since 4.22.0. It is enabled by default in 4.22 and below and disabled by default in the LTS line. The docs strongly recommend upgrading instead of disabling it.
grep -rn "versionCheck" src/2Fix
Turn it off on the editor config only as a stop-gap, and plan the upgrade. This hides the message and does not make the editor secure.
CKEDITOR.replace('editor1', {
versionCheck: false,
});3Verify
Reload the page. The bar should no longer appear.
CKEDITOR.instances.editor1.config.versionCheckConfirmed by ckeditor.com
How do I stop it coming back?
- Put the CKEditor upgrade or replacement on the roadmap, and note that the open-source 4.22.1 line gets no fixes.
- Sanitize rich text on the server too, whatever editor produced it.
- Check the editor release notes when you review dependencies.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Projects of mine built on the same technologies:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix