CVE-2019-14469 Nexus Repository 3 - Cross Site Scripting XSS - 2019-07-26

Date:  July 26, 2019

Affected Versions:  Nexus Repository 3 versions starting in 3.14.0 up to and including 3.17.0

Fixed in Version:  Nexus Repository 3 Pro version 3.18.0

Risk: Low - 3.1 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N)


A cross-site scripting (XSS) vulnerability have been discovered in Nexus Repository 3.

An attacker with elevated privileges can create entities with specially crafted properties which when viewed by another user can execute arbitrary JavaScript in the context of the Nexus Repository application.  We have fixed the issue by ensuring the values are properly encoded. This advisory provides the pertinent information needed to properly address this vulnerability, along with the details on how to reach us if you have any further questions or concerns.

We are not aware of any active exploits taking advantage of this issue. However, we strongly encourage all users of Nexus Repository 3 to immediately take the steps outlined in this advisory.

The identified vulnerability allows arbitrary JavaScript to run in an Nexus Repository 3 user's browser in the context of the application.  In regards to XSS, it is common that the injected JavaScript could forge requests on behalf of the user, redirect the user to another site or modify the page content.  We are highly recommending all instances of Nexus Repository 3 be upgraded to 3.18.0 or later. The latest version can be downloaded from:

For detailed information on upgrade, please see:

Upgrading Nexus Repository Manager 3.1.0 and Newer


Thank you to 1jesper1 for reporting the vulnerability.


If you run into any problems, or have any questions/concerns, please contact us by filing a ticket at

Frequently Asked Questions:

Q:  What is the risk associated with this vulnerability?

A: An attacker with elevated privileges can create entities with specially crafted properties which when viewed would execute arbitrary JavaScript within the context of the application leading to the compromise of the confidentiality and integrity of data.  


Q: What preconditions must be met in order to be vulnerable?

A: An attacker must have elevated privileges and another user must view malicious entities.


Q: Are there implications associated with this advisory itself?

A: Disclosure unfortunately means bad actors may try to take advantage.  While we have initially limited the information to the minimum details necessary for users to affect an appropriate fix, this merely slows down a would be attacker.  As such, we are advising all organizations utilizing Nexus Repository 3 to immediately assess their individual impact and take appropriate action in response.


Q:  Where can I obtain more information associated with the vulnerability?

A:  At this time, and in the interest of best protecting our user community, we are limiting the information released to that absolutely required in order to assess impact and affect remediation. Please contact support for more information.


Q:  Why is Sonatype making this information available?

A:  This is part of a responsible disclosure process.  Given Nexus Repository is an open source project with widespread usage, notifying the user base will invariably lead to broad dissemination.  We are taking a concerted and proactive approach in our outreach activities and an effort to achieve the most rapid remediation possible.

Have more questions? Submit a request


Article is closed for comments.