### 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.
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
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
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.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.