VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

yui: vulnerability history, versions and safety

yui is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 54 releases, from Sep 2020 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
i
2 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 yui vulnerabilities

Vulert verdict on yui 3.18.1 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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 3.18.1 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 5.3 i
  • With no published fix 2 i
  • Depended on by 128 packages i
  • Stars 4,161 i
  • OpenSSF scorecard 1/10 i
  • Last release 144 months ago i
  • Licence non-standard 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 yui, 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
3.18.1 22 Oct 2014 M2 — No Details →
3.18.0 29 Sep 2014 M2 — No Details →
3.17.2 02 Jun 2014 M2 — No Details →
3.17.2-rc-1 23 May 2014 M2 — No Details →
3.17.1 21 May 2014 M2 — No Details →
3.17.0 19 May 2014 M2 — No Details →
3.17.0-rc-1 13 May 2014 M2 — No Details →
3.16.0 10 Apr 2014 M2 — No Details →
3.16.0-rc-1 03 Apr 2014 M2 — No Details →
3.15.0 25 Feb 2014 M2 — No Details →
3.15.0-rc-1 20 Feb 2014 M2 — No Details →
3.14.1 18 Dec 2013 M2 — No Details →
3.14.0 25 Nov 2013 M2 — No Details →
3.14.0-rc-1 21 Nov 2013 M2 — No Details →
3.13.0 07 Oct 2013 M2 — No Details →
3.13.0-rc-1 01 Oct 2013 M2 — No Details →
3.13.0-beta-1 04 Sep 2013 M2 — No Details →
3.12.0 28 Aug 2013 M2 — No Details →
3.12.0-beta-1 15 Aug 2013 M2 — No Details →
3.11.0 16 Jul 2013 M2 — No Details →
3.11.0pr1 19 Jun 2013 M2 — No Details →
3.10.2 06 Jun 2013 M4 — No Details →
3.10.3 06 Jun 2013 M3 — No Details →
3.10.1 14 May 2013 M4 — No Details →
3.9.1 04 May 2013 M4 — No Details →
3.9.0pr3 04 May 2013 M4 — No Details →
3.9.0pr2 04 May 2013 M4 — No Details →
3.9.0pr1 04 May 2013 M4 — No Details →
3.9.0 04 May 2013 M4 — No Details →
3.8.1 04 May 2013 M4 — No Details →
3.8.0pr2 04 May 2013 M4 — No Details →
3.8.0pr1 04 May 2013 M4 — No Details →
3.8.0 04 May 2013 M4 — No Details →
3.7.3 04 May 2013 M4 — No Details →
3.7.2 04 May 2013 M4 — No Details →
3.7.1 04 May 2013 M4 — No Details →
3.7.0pr4 04 May 2013 M4 — No Details →
3.7.0pr3 04 May 2013 M4 — No Details →
3.7.0pr2 04 May 2013 M4 — No Details →
3.7.0pr1 04 May 2013 M4 — No Details →
3.7.0 03 May 2013 M4 — No Details →
3.6.0pr3 03 May 2013 M4 — No Details →
3.6.0pr2 03 May 2013 M4 — No Details →
3.6.0pr1 03 May 2013 M4 — No Details →
3.6.0 03 May 2013 M4 — No Details →
3.5.1 03 May 2013 M4 — No Details →
3.5.1-2 03 May 2013 M4 — No Details →
3.5.1-1 03 May 2013 M4 — No Details →
3.5.0pr4 03 May 2013 M4 — No Details →
3.5.0pr2 03 May 2013 M4 — No Details →
3.5.0PR1 03 May 2013 M4 — No Details →
3.10.0pr1 03 May 2013 M4 — No Details →
3.5.0 03 May 2013 M4 — No Details →
3.10.0 23 Apr 2013 M4 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 3

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

03 Vulnerabilities

Recorded vulnerabilities for yui

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-4941: YUI Uploader Component XSS Vulnerability 5.3 medium No fix published 13 May 2022
CVE-2013-4942: YUI Cross-site Scripting (XSS) Vulnerability in Moodle and YUI 5.3 medium No fix published 13 May 2022
CVE-2013-4940: YUI Cross-site Scripting (XSS) Vulnerability in Moodle and YUI 5.3 medium 3.10.11 13 May 2022
CVE-2013-4939: Cross-Site Scripting in yui N/A medium 3.10.3 01 Sep 2020

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 yui

Is yui safe to use?

Vulert records 4 vulnerabilities for yui in npm: 0 critical, 0 high, 4 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is yui's Vulert package health score?

Vulert scores yui 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 yui affected?

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

Which version of yui should I use?

3.18.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 yui have?

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

0 vulnerabilities were recorded for yui in the last 12 months, and the oldest entry in this database dates to 01 Sep 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 yui 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 yui for upcoming vulnerabilities?

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