CVE-2019-14772: Cross-Site Scripting (XSS) in Verdaccio

verdaccio Updated 02 Oct 2025

Summary

29/05/2019
Yes i
Moderate
6.1

CVE-2019-14772: Cross-Site Scripting (XSS) in Verdaccio. Affects verdaccio versions < 3.12.0. Fixed in 3.12.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Verdaccio is an open-source package registry for the npm ecosystem. It allows users to host their own private npm registry and manage packages. The vulnerability in Verdaccio allows for Cross-Site Scripting (XSS) attacks, where malicious packages containing JavaScript code can be executed in the user interface, potentially leading to the theft of user credentials.

Vulnerability Detail

The vulnerability in Verdaccio is classified as Cross-Site Scripting (XSS). It occurs when malicious packages with JavaScript content are executed in the user interface, enabling attackers to steal user credentials. This vulnerability can have serious consequences, as it allows unauthorized access to sensitive information and can lead to further exploitation of the system.

How To Fix

Minimum fixed version

3.12.0

This is the first release that contains the fix.

npm install verdaccio@3.12.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There are no known workarounds for this vulnerability. Users must update their Verdaccio installation to the recommended versions to mitigate the risk of XSS attacks.

Conclusion

In conclusion, the vulnerability in Verdaccio allows for Cross-Site Scripting (XSS) attacks, which can result in the theft of user credentials. To mitigate this risk, users should upgrade their Verdaccio installation to version 3.12.0 or higher, or migrate to a major version equal to or greater than 4.0.0. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for verdaccio →

Share this vulnerability

FAQ

The vulnerability allows for Cross-Site Scripting (XSS) attacks, which can lead to the theft of user credentials and unauthorized access to sensitive information.

Yes, the vulnerability has been patched in Verdaccio versions 3.12.0 and higher, as well as major versions equal to or greater than 4.0.0.

No, users must upgrade their Verdaccio installation to the recommended versions to fix the vulnerability.

You can find more information about this vulnerability in the NPMJS Security Team advisories:

The vulnerability was reported by the NPMJS Security Team.

How To Fix

Minimum fixed version

3.12.0

This is the first release that contains the fix.

npm install verdaccio@3.12.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

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 →
Help improve this record
Report an issue or send feedback