VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

vditor: vulnerability history, versions and safety

vditor is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 120 releases, from Jan 2022 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded M5
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 vditor vulnerabilities

Vulert verdict on vditor 4.0.1 i

Updated on 23 Oct 2026

Careful: 4.0.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • 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 4.0.1 — affected i
  • Vulnerabilities on record 5 over 2 years · 0 in the last year i
  • Latest disclosure 03 May 2024 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Depended on by 1 packages i
  • Stars 11,380 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 vditor, 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.0.1 18 Oct 2026 M1 MIT No Details →
4.0.0 30 Aug 2026 M1 MIT No Details →
3.11.3 11 Aug 2026 M1 MIT No Details →
3.11.2 02 Sep 2025 M1 MIT No Details →
3.11.1 27 May 2025 M1 MIT No Details →
3.11.0 09 Apr 2025 M1 MIT No Details →
3.10.9 11 Feb 2025 M1 MIT No Details →
3.10.8 03 Dec 2024 M1 MIT No Details →
3.10.7 15 Oct 2024 M1 MIT No Details →
3.10.6 11 Sep 2024 M1 MIT No Details →
3.10.5 09 Aug 2024 M1 MIT No Details →
3.10.4 16 Apr 2024 M1 MIT No Details →
3.10.3 02 Apr 2024 M1 MIT No Details →
3.10.2 19 Mar 2024 M1 MIT No Details →
3.10.1 05 Mar 2024 M1 MIT No Details →
3.9.9 30 Jan 2024 M1 MIT No Details →
3.9.8 26 Dec 2023 M1 MIT No Details →
3.9.7 14 Dec 2023 M1 MIT No Details →
3.9.6 26 Sep 2023 M1 MIT No Details →
3.9.5 29 Aug 2023 M1 MIT No Details →
3.9.4 20 Jun 2023 M1 MIT No Details →
3.9.3 23 May 2023 M1 MIT No Details →
3.9.2 11 Apr 2023 M1 MIT No Details →
3.9.1 14 Mar 2023 M1 MIT No Details →
3.9.0 15 Jan 2023 M1 MIT No Details →
3.8.18 01 Nov 2022 M1 MIT No Details →
3.8.17 04 Aug 2022 M1 MIT No Details →
3.8.16 04 Aug 2022 M1 MIT No Details →
3.8.15 24 May 2022 M1 MIT No Details →
3.8.14 11 May 2022 M1 MIT No Details →
3.8.13 31 Mar 2022 M1 MIT No Details →
3.8.12 03 Mar 2022 M2 MIT No Details →
3.8.11 22 Jan 2022 M2 MIT No Details →
3.8.10 21 Dec 2021 M4 MIT No Details →
3.8.9 21 Dec 2021 M4 MIT No Details →
3.8.8 05 Dec 2021 M4 MIT No Details →
3.8.7 21 Sep 2021 M4 MIT No Details →
3.8.6 06 Jul 2021 M5 MIT No Details →
3.8.5 13 May 2021 M5 MIT No Details →
3.8.4 26 Mar 2021 M5 MIT No Details →
3.8.3 14 Mar 2021 M5 MIT No Details →
3.8.2 02 Mar 2021 M5 MIT No Details →
3.8.1 04 Feb 2021 M5 MIT No Details →
3.8.0 31 Jan 2021 M5 MIT No Details →
3.7.7 19 Jan 2021 M5 MIT No Details →
3.7.6 17 Jan 2021 M5 MIT No Details →
3.7.5 06 Jan 2021 M5 MIT No Details →
3.7.4 25 Dec 2020 M5 MIT No Details →
3.7.3 18 Dec 2020 M5 MIT No Details →
3.7.2 14 Dec 2020 M5 MIT No Details →
3.7.1 06 Dec 2020 M5 MIT No Details →
3.7.0 01 Dec 2020 M5 MIT No Details →
3.6.6 23 Nov 2020 M5 MIT No Details →
3.6.5 23 Nov 2020 M5 MIT No Details →
3.6.4 23 Nov 2020 M5 MIT No Details →
3.6.3 19 Nov 2020 M5 MIT No Details →
3.6.2 13 Nov 2020 M5 MIT No Details →
3.6.1 10 Nov 2020 M5 MIT No Details →
3.6.0 27 Oct 2020 M5 MIT No Details →
3.5.5 12 Oct 2020 M5 MIT No Details →
3.5.4 20 Sep 2020 M5 MIT No Details →
3.5.3 09 Sep 2020 M5 MIT No Details →
3.5.2 06 Sep 2020 M5 MIT No Details →
3.5.1 30 Aug 2020 M5 MIT No Details →
3.5.0 30 Aug 2020 M5 MIT No Details →
3.4.7 22 Aug 2020 M5 MIT No Details →
3.4.6 11 Aug 2020 M5 MIT No Details →
3.4.5 07 Aug 2020 M5 MIT No Details →
3.4.4 05 Aug 2020 M5 MIT No Details →
3.4.3 03 Aug 2020 M5 MIT No Details →
3.4.2 03 Aug 2020 M5 MIT No Details →
3.4.1 31 Jul 2020 M5 MIT No Details →
3.4.0 29 Jul 2020 M5 MIT No Details →
3.3.12 28 Jul 2020 M5 MIT No Details →
3.3.11 24 Jul 2020 M5 MIT No Details →
3.3.10 20 Jul 2020 M5 MIT No Details →
3.3.9 18 Jul 2020 M5 MIT No Details →
3.3.8 16 Jul 2020 M5 MIT No Details →
3.3.7 16 Jul 2020 M5 MIT No Details →
3.3.6 10 Jul 2020 M5 MIT No Details →
3.3.5 09 Jul 2020 M5 MIT No Details →
3.3.4 08 Jul 2020 M5 MIT No Details →
3.3.3 23 Jun 2020 M5 MIT No Details →
3.3.2 18 Jun 2020 M5 MIT No Details →
3.3.1 18 Jun 2020 M5 MIT No Details →
3.3.0 15 Jun 2020 M5 MIT No Details →
3.2.12 06 Jun 2020 M5 MIT No Details →
3.2.11 06 Jun 2020 M5 MIT No Details →
3.2.10 27 May 2020 M5 MIT No Details →
3.2.9 22 May 2020 M5 MIT No Details →
3.2.8 20 May 2020 M5 MIT No Details →
3.2.7 17 May 2020 M5 MIT No Details →
3.2.6 14 May 2020 M5 MIT No Details →
3.2.5 13 May 2020 M5 MIT No Details →
3.2.4 12 May 2020 M5 MIT No Details →
3.2.3 09 May 2020 M5 MIT No Details →
3.2.2 08 May 2020 M5 MIT No Details →
3.2.1 07 May 2020 M5 MIT No Details →
3.2.0 06 May 2020 M5 MIT No Details →
3.1.23 05 May 2020 M5 MIT No Details →
3.1.22 04 May 2020 M5 — No Details →
3.1.21 02 May 2020 M5 — No Details →
3.1.20 29 Apr 2020 M5 — No Details →
3.1.19 26 Apr 2020 M5 — No Details →
3.1.18 24 Apr 2020 M5 — No Details →
3.1.17 24 Apr 2020 M5 — No Details →
3.1.16 23 Apr 2020 M5 — No Details →
3.1.15 21 Apr 2020 M5 — No Details →
3.1.14 19 Apr 2020 M5 — No Details →
3.1.13 19 Apr 2020 M5 — No Details →
3.1.12 17 Apr 2020 M5 — No Details →
3.1.11 16 Apr 2020 M5 — No Details →
3.1.10 15 Apr 2020 M5 — No Details →
3.1.9 14 Apr 2020 M5 — No Details →
3.1.8 14 Apr 2020 M5 — No Details →
3.1.7 14 Apr 2020 M5 — No Details →
3.1.6 12 Apr 2020 M5 — No Details →
3.1.5 11 Apr 2020 M5 — No Details →
3.1.4 10 Apr 2020 M5 — No Details →
3.1.3 08 Apr 2020 M5 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3
  • 2023 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for vditor

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-32855: Vditor Cross-site Scripting vulnerability 6.1 medium 3.8.7 21 Feb 2023
CVE-2022-0350: Cross-site Scripting in vditor 5.4 medium 3.8.13 01 Apr 2022
CVE-2021-4103: Cross-site Scripting in vditor 5.4 medium 3.8.11 28 Jan 2022
CVE-2022-0341: Cross-site Scripting in vditor 5.4 medium 3.8.11 15 Mar 2022
CVE-2024-34449: Cross-site Scripting in Vditor N/A medium No fix published 03 May 2024

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 vditor

Is vditor safe to use?

Vulert records 5 vulnerabilities for vditor in npm: 0 critical, 0 high, 5 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is vditor's Vulert package health score?

Vulert scores vditor 60/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 vditor affected?

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

How many vulnerabilities does vditor have?

5 vulnerabilities are recorded for vditor in the npm ecosystem: 0 critical, 0 high, 5 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 vditor vulnerabilities disclosed?

0 vulnerabilities were recorded for vditor in the last 12 months, and the oldest entry in this database dates to 28 Jan 2022. 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 vditor 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 vditor for upcoming vulnerabilities?

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