Skip to main content
CVE-2025-13488VulnerabilityPublished

CVE-2025-13488: Sonatype Nexus Repository · XSS or 'Cross-site Scripting'

Affects Sonatype Nexus RepositorySource CVE Database V5

0

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
5.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.sonatype.nexus/nexus-repositorypkg:maven/org.sonatype.nexus/nexus-repositoryOther threatsAffected
  • =3.83.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2025-13488, European organizations should implement several specific measures beyond generic advice: 1) Immediately restrict repository upload privileges to only trusted and verified users, minimizing the number of accounts that can upload content. 2) Implement strict content validation and sanitization policies on uploaded artifacts, including scanning for embedded scripts or suspicious content before acceptance. 3) Monitor repository logs and user activity for unusual upload patterns or access behaviors that could indicate exploitation attempts. 4) Configure web application firewalls (WAFs) to detect and block XSS payloads targeting the Nexus Repository interface. 5) Encourage developers and users to avoid clicking on suspicious links or content served from the repository until a patch is available. 6) Engage with Sonatype support or security advisories to obtain patches or updates addressing this regression and apply them promptly once released. 7) Consider isolating the Nexus Repository instance within a segmented network zone with strict access controls to limit exposure. 8) Educate repository users about the risks of XSS and safe browsing practices within internal tools. These targeted actions will reduce the likelihood and impact of exploitation while awaiting official remediation.

Description

Due to a regression introduced in version 3.83.0, a security header is no longer applied to certain user-uploaded content served from repositories. This may allow an authenticated attacker with repository upload privileges to exploit a stored cross-site scripting (XSS) vulnerability with user context.

References

Community reviews

Loading reviews…