Skip to main content
VulnerabilityPublished Updated

CVE-2024-45478: Apache Ranger · Cross-site Scripting

Affects Apache RangerSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.ranger/rangerpkg:maven/org.apache.ranger/rangerOther threatsAffected
  • =2.4.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

European organizations should prioritize upgrading Apache Ranger installations from version 2.4.0 to 2.5.0 or later to remediate this vulnerability. Beyond patching, organizations should enforce strict access controls and minimize the number of users with high privileges in the Ranger UI. Implement multi-factor authentication (MFA) for administrative access to reduce the risk of credential compromise. Conduct regular audits of user activities within the Ranger UI to detect anomalous behavior indicative of exploitation attempts. Additionally, organizations should consider implementing web application firewalls (WAFs) with rules to detect and block XSS payloads targeting the Ranger UI. Security teams should also educate administrators about the risks of stored XSS and the importance of cautious input handling. Finally, ensure that all input fields in custom extensions or integrations with Ranger are properly sanitized and encoded to prevent similar vulnerabilities.

Description

Stored XSS vulnerability in Edit Service Page of Apache Ranger UI in Apache Ranger Version 2.4.0. Users are recommended to upgrade to version Apache Ranger 2.5.0, which fixes this issue.

References

Community reviews

Loading reviews…