VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

ckeditor: vulnerability history, versions and safety

ckeditor is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 19 releases, first recorded in Nov 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ckeditor vulnerabilities

Vulert verdict on ckeditor 4.12.1 i

Updated on 23 Oct 2026

Good news: 4.12.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Widely used
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

What to do: Stay on 4.12.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.12.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.12.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 21 Nov 2018 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 139 packages i
  • Stars 518 i
  • OpenSSF scorecard 2/10 i
  • Last release 87 months ago i
  • Licence GPL-2.0 OR LGPL-2.1 OR MPL-1.1 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for ckeditor, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.12.1 28 Jun 2019 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.12.0 27 Jun 2019 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.11.4 09 Apr 2019 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.11.3 26 Feb 2019 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.11.2 10 Jan 2019 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.11.1 08 Nov 2018 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.11.0 07 Nov 2018 none GPL-2.0 OR LGPL-2.1 OR MPL-1.1 — Details →
4.10.1 12 Sep 2018 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.10.0 03 Jul 2018 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.9.2 18 Apr 2018 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.9.1 26 Mar 2018 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.9.0 15 Mar 2018 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.8.0 13 Dec 2017 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.7.3 13 Sep 2017 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.7.2 17 Aug 2017 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.7.1 28 Jun 2017 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.7.0 25 May 2017 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.6.2 12 Jan 2017 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.6.1 08 Dec 2016 M1 GPL-2.0 OR LGPL-2.1 OR MPL-1.1 Yes Details →
4.6.0 16 Nov 2016 M1 non-standard Yes Details →
4.5.11 07 Sep 2016 M1 non-standard Yes Details →
4.5.10 13 Jul 2016 M1 non-standard Yes Details →
4.5.9 12 May 2016 M1 non-standard Yes Details →
4.5.8 31 Mar 2016 M1 non-standard Yes Details →
4.5.7 04 Feb 2016 M1 non-standard Yes Details →
4.5.6 26 Jan 2016 M1 non-standard Yes Details →

All 26 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ckeditor

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-17960: ckeditor - User-Assisted XSS Vulnerability 6.1 medium 4.11.0 21 Nov 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ckeditor

Is ckeditor safe to use?

Vulert records 1 vulnerabilities for ckeditor in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ckeditor's Vulert package health score?

Vulert scores ckeditor 45/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of ckeditor affected?

No. 4.12.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of ckeditor should I use?

4.12.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does ckeditor have?

1 vulnerability is recorded for ckeditor in the npm ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ckeditor vulnerabilities disclosed?

0 vulnerabilities were recorded for ckeditor in the last 12 months, and the oldest entry in this database dates to 21 Nov 2018. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ckeditor are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ckeditor for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ckeditor version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.