Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

verdaccio before 3.12.0 allows XSS.

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2019-14772

Published

verdaccio before 3.12.0 allows XSS.

Source published
8 Aug 2019 12:59:04 UTC
Source modified
5 Aug 2024 00:26:38 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

euvd · EUVD-2019-0457

Published

verdaccio before 3.12.0 allows XSS.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 8, 2019, 12:59:04 PM

dateUpdated: Aug 5, 2024, 12:26:38 AM

Source published
Aug 8, 2019, 12:59:04 PM (timezone not stated)
Source modified
Aug 5, 2024, 12:26:38 AM (timezone not stated)
Saved here
17 Nov 2026 22:34:32 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

nvd · CVE-2019-14772

Published

verdaccio before 3.12.0 allows XSS.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-79

Original publisher date fields

published: 2019-08-08T13:15:12.923

lastModified: 2026-06-17T02:18:59.253

1 source CPE criteria · context only
  • cpe:2.3:a:verdaccio:verdaccio:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
8 Aug 2019 13:15:12 UTC
Source modified
17 Jun 2026 02:18:59 UTC
Saved here
24 Oct 2026 15:17:27 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.0 · [email protected] · Primary · 6.1 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CVSS 2.0 · [email protected] · Primary · 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

osv · GHSA-78j5-gcmf-vqc8

Published

### Impact What kind of vulnerability is it? Who is impacted? Cross-Site Scripting XSS, malicious packages with content Javascript that might be executed in the User Interface stealing user credentials. ### Patches Has the problem been patched? What versions should users upgrade to? Users that still using `v3` must upgrade to **>3.12.0** or those have no problem to migrate to a major version **>=4.0.0** also fix the issue. ### Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? No, the users must update. ### References Are there any links users can visit to find out more? https://www.npmjs.com/advisories/832 https://www.npmjs.com/advisories/833 The issue was reported by the NPMJS Security Team ### For more information If you have any questions or comments about this advisory: * Read the Security Policy to find the ways to be in contact with us.

Source published
29 May 2019 18:02:59 UTC
Source modified
10 Sep 2026 03:48:11 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 06:56 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current