VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

tinymce: vulnerability history, versions and safety

tinymce is a package in the npm ecosystem. Vulert records 32 vulnerabilities for it across 120 releases, from Jan 2020 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
32 vulnerabilities recorded H5 M26 L1
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
4 in the last 12 months

Most recent disclosure 05 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all tinymce vulnerabilities

Vulert verdict on tinymce 8.10.0 i

Updated on 22 Oct 2026

Careful: 8.10.0 has 5 known vulnerabilities, and 5 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 8.10.0 — affected i
  • Vulnerabilities on record 32 over 6 years · 4 in the last year i
  • Latest disclosure 05 Jun 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 5 i
  • Depended on by 75 packages i
  • Stars 16,316 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence non-standard 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 tinymce, 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
8.10.0 14 Oct 2026 H3 M2 non-standard No Details →
8.9.3 06 Oct 2026 H3 M2 non-standard No Details →
8.9.2 23 Sep 2026 H3 M2 non-standard No Details →
8.9.1 09 Sep 2026 H3 M2 non-standard No Details →
8.9.0 31 Aug 2026 H3 M2 non-standard No Details →
8.8.2 27 Jul 2026 H3 M2 non-standard No Details →
8.8.1 22 Jul 2026 H3 M2 non-standard No Details →
8.8.0 15 Jul 2026 H3 M2 non-standard No Details →
8.7.0 02 Jul 2026 H3 M2 non-standard No Details →
8.6.0 03 Jun 2026 H3 M2 non-standard No Details →
7.9.3 20 May 2026 H3 M2 GPL-2.0-or-later No Details →
8.5.1 20 May 2026 H3 M2 non-standard No Details →
8.5.0 29 Apr 2026 H3 M2 non-standard No Details →
8.4.0 31 Mar 2026 H3 M2 non-standard No Details →
7.9.2 11 Feb 2026 H3 M2 GPL-2.0-or-later No Details →
8.3.2 14 Jan 2026 H3 M2 non-standard No Details →
8.3.1 17 Dec 2025 H3 M2 non-standard No Details →
8.3.0 10 Dec 2025 H3 M2 non-standard No Details →
8.2.2 17 Nov 2025 H3 M2 GPL-2.0-or-later No Details →
8.2.1 06 Nov 2025 H3 M2 GPL-2.0-or-later No Details →
8.2.0 23 Oct 2025 H3 M2 GPL-2.0-or-later No Details →
8.1.2 18 Sep 2025 H3 M2 GPL-2.0-or-later No Details →
8.1.1 17 Sep 2025 H3 M2 GPL-2.0-or-later No Details →
8.1.0 17 Sep 2025 H3 M2 GPL-2.0-or-later No Details →
8.0.2 14 Aug 2025 H3 M2 GPL-2.0-or-later No Details →
8.0.1 28 Jul 2025 H3 M2 GPL-2.0-or-later No Details →
8.0.0 23 Jul 2025 H3 M2 GPL-2.0-or-later No Details →
6.8.6 29 May 2025 H4 M2 MIT No Details →
7.9.1 29 May 2025 H3 M2 GPL-2.0-or-later No Details →
7.9.0 15 May 2025 H3 M2 GPL-2.0-or-later No Details →
7.8.0 09 Apr 2025 H3 M2 GPL-2.0-or-later No Details →
7.7.2 19 Mar 2025 H3 M2 GPL-2.0-or-later No Details →
7.7.1 05 Mar 2025 H3 M2 GPL-2.0-or-later No Details →
7.7.0 20 Feb 2025 H3 M2 GPL-2.0-or-later No Details →
7.6.1 22 Jan 2025 H3 M2 GPL-2.0-or-later No Details →
7.6.0 11 Dec 2024 H3 M2 GPL-2.0-or-later No Details →
7.5.1 13 Nov 2024 H3 M2 GPL-2.0-or-later No Details →
7.5.0 06 Nov 2024 H3 M2 GPL-2.0-or-later No Details →
6.8.5 10 Oct 2024 H4 M2 MIT No Details →
7.4.1 10 Oct 2024 H3 M2 GPL-2.0-or-later No Details →
7.4.0 09 Oct 2024 H3 M2 GPL-2.0-or-later No Details →
7.3.0 07 Aug 2024 H3 M2 GPL-2.0-or-later No Details →
7.2.1 03 Jul 2024 H3 M2 GPL-2.0-or-later No Details →
6.8.4 19 Jun 2024 H4 M2 MIT No Details →
7.2.0 19 Jun 2024 H3 M2 GPL-2.0-or-later No Details →
7.1.2 05 Jun 2024 H3 M2 GPL-2.0-or-later No Details →
7.1.1 22 May 2024 H3 M2 GPL-2.0-or-later No Details →
7.1.0 08 May 2024 H3 M2 GPL-2.0-or-later No Details →
7.0.1 10 Apr 2024 H4 M2 GPL-2.0-or-later No Details →
7.0.0 20 Mar 2024 H4 M2 GPL-2.0-or-later No Details →
6.8.3 08 Feb 2024 H4 M2 MIT No Details →
6.8.2 11 Dec 2023 H4 M2 MIT No Details →
6.8.1 29 Nov 2023 H4 M2 MIT No Details →
6.8.0 22 Nov 2023 H4 M3 MIT No Details →
5.10.9 15 Nov 2023 H3 M5 LGPL-2.1 No Details →
6.7.3 15 Nov 2023 H3 M3 MIT No Details →
6.7.2 25 Oct 2023 H3 M3 MIT No Details →
6.7.1 19 Oct 2023 H3 M3 MIT No Details →
5.10.8 19 Oct 2023 H3 M6 LGPL-2.1 No Details →
6.7.0 30 Aug 2023 H3 M5 MIT No Details →
6.6.2 09 Aug 2023 H3 M5 MIT No Details →
6.6.1 02 Aug 2023 H3 M5 MIT No Details →
6.6.0 12 Jul 2023 H3 M5 MIT No Details →
6.5.1 19 Jun 2023 H3 M5 MIT No Details →
6.5.0 13 Jun 2023 H3 M5 MIT No Details →
6.4.2 26 Apr 2023 H3 M5 MIT No Details →
6.4.1 29 Mar 2023 H3 M5 MIT No Details →
6.4.0 16 Mar 2023 H3 M5 MIT No Details →
6.3.2 22 Feb 2023 H3 M5 MIT No Details →
5.10.7 07 Dec 2022 H3 M6 LGPL-2.1 No Details →
6.3.1 06 Dec 2022 H3 M5 MIT No Details →
6.3.0 23 Nov 2022 H3 M8 MIT No Details →
5.10.6 19 Oct 2022 H3 M6 LGPL-2.1 No Details →
6.2.0 08 Sep 2022 H3 M8 MIT No Details →
6.1.2 29 Jul 2022 H3 M8 MIT No Details →
6.1.1 27 Jul 2022 H3 M8 MIT No Details →
6.1.0 29 Jun 2022 H3 M8 MIT No Details →
6.0.3 25 May 2022 H3 M8 MIT No Details →
5.10.5 25 May 2022 H3 M6 LGPL-2.1 No Details →
6.0.2 27 Apr 2022 H3 M8 MIT No Details →
5.10.4 27 Apr 2022 H3 M6 LGPL-2.1 No Details →
6.0.1 23 Mar 2022 H3 M8 MIT No Details →
6.0.0 03 Mar 2022 H3 M8 MIT No Details →
5.10.3 09 Feb 2022 H3 M6 LGPL-2.1 No Details →
5.10.2 17 Nov 2021 H3 M6 LGPL-2.1 No Details →
5.10.1 03 Nov 2021 H3 M6 LGPL-2.1 No Details →
5.10.0 11 Oct 2021 H3 M6 LGPL-2.1 No Details →
5.9.2 08 Sep 2021 H3 M10 LGPL-2.1 No Details →
5.9.1 27 Aug 2021 H3 M10 LGPL-2.1 No Details →
5.9.0 26 Aug 2021 H3 M10 LGPL-2.1 No Details →
5.8.2 23 Jun 2021 H3 M14 LGPL-2.1 No Details →
5.8.1 20 May 2021 H3 M14 LGPL-2.1 No Details →
5.8.0 06 May 2021 H3 M14 LGPL-2.1 No Details →
5.7.1 17 Mar 2021 H3 M14 LGPL-2.1 No Details →
5.7.0 10 Feb 2021 H3 M15 LGPL-2.1 No Details →
5.6.2 08 Dec 2020 H3 M15 LGPL-2.1 No Details →
5.6.1 25 Nov 2020 H3 M15 LGPL-2.1 No Details →
5.6.0 18 Nov 2020 H3 M15 LGPL-2.1 No Details →
5.5.1 01 Oct 2020 H3 M18 L1 LGPL-2.1 No Details →
5.5.0 29 Sep 2020 H3 M18 L1 LGPL-2.1 No Details →
5.4.2 17 Aug 2020 H3 M18 L1 — No Details →
4.5.12 14 Jul 2020 H4 M21 L1 — No Details →
4.9.11 13 Jul 2020 H3 M18 L1 — No Details →
5.4.1 08 Jul 2020 H3 M18 L1 — No Details →
5.4.0 30 Jun 2020 H3 M18 L1 — No Details →
5.3.2 10 Jun 2020 H3 M18 L1 — No Details →
5.3.1 27 May 2020 H3 M18 L1 — No Details →
5.3.0 21 May 2020 H3 M18 L1 — No Details →
5.2.2 23 Apr 2020 H3 M18 L1 — No Details →
4.9.10 23 Apr 2020 H3 M19 L1 — No Details →
4.9.9 25 Mar 2020 H3 M20 L1 — No Details →
5.2.1 25 Mar 2020 H3 M18 L1 — No Details →
5.2.0 13 Feb 2020 H3 M18 L1 — No Details →
5.1.6 28 Jan 2020 H3 M18 L1 — No Details →
4.9.8 28 Jan 2020 H3 M20 L1 — No Details →
5.1.5 19 Dec 2019 H3 M18 L1 — No Details →
4.9.7 19 Dec 2019 H3 M20 L1 — No Details →
5.1.4 11 Dec 2019 H3 M18 L1 — No Details →
5.1.3 04 Dec 2019 H3 M18 L1 — No Details →
5.1.2 19 Nov 2019 H3 M18 L1 — No Details →

The newest 120 of 225 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 3
  • 2021 13
  • 2022 3
  • 2023 3
  • 2024 6
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for tinymce

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-47761: TinyMCE Cross-Site Scripting (XSS) Vulnerability via Media Plugin Injection 8.7 high No fix published 05 Jun 2026
CVE-2026-47760: TinyMCE XSS Vulnerability via SVG Sanitization Bypass 8.7 high 7.1.0 05 Jun 2026
CVE-2026-47759: TinyMCE Cross-Site Scripting (XSS) Vulnerability via data-mce-* Attributes 8.7 high No fix published 05 Jun 2026
CVE-2026-47762: TinyMCE Cross-Site Scripting (XSS) Vulnerability via mce:protected Comments 8.7 high No fix published 05 Jun 2026
Cross-site scripting vulnerability in TinyMCE plugins 6.1 medium 5.10.0 02 Nov 2021

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 tinymce

Is tinymce safe to use?

Vulert records 32 vulnerabilities for tinymce in npm: 0 critical, 5 high, 26 medium and 1 low. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is tinymce's Vulert package health score?

Vulert scores tinymce 50/100, which reads as usable, but worth attention. 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 current release has a vulnerability with no published fix, which caps this score.

Is the latest version of tinymce affected?

Yes. 8.10.0, the version you would install today, has 5 known vulnerabilities, and 5 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does tinymce have?

32 vulnerabilities are recorded for tinymce in the npm ecosystem: 0 critical, 5 high, 26 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new tinymce vulnerabilities disclosed?

4 vulnerabilities were recorded for tinymce in the last 12 months, and the oldest entry in this database dates to 30 Jan 2020. 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 tinymce 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 tinymce for upcoming vulnerabilities?

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