Skip to main content
CVE-2024-47090VulnerabilityPublished

CVE-2024-47090: Nagvis · Cross-site Scripting

Affects NagvisSource 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.2% chance of exploitation in 30 days – higher than 13% 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:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 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
Nagvis NagvisAffected
  • =1.9.0
Fixed in–

AI-suggested

To mitigate CVE-2024-47090, European organizations should prioritize upgrading Nagvis installations to version 1.9.47 or later, where the vulnerability has been addressed. If immediate upgrading is not feasible, organizations should implement strict input validation and output encoding on any user-supplied data rendered by Nagvis, potentially through web application firewalls (WAFs) configured to detect and block XSS payloads targeting Nagvis endpoints. Network segmentation should be enforced to restrict access to Nagvis dashboards only to trusted users and devices. Multi-factor authentication (MFA) should be enabled for Nagvis user accounts to reduce the risk of session hijacking. Additionally, organizations should educate users about the risks of clicking untrusted links or interacting with suspicious content within the monitoring environment. Regular monitoring and logging of Nagvis access and user activities can help detect anomalous behavior indicative of exploitation attempts. Finally, security teams should review and harden the overall security posture of monitoring infrastructure, ensuring that Nagvis is deployed behind secure reverse proxies with HTTPS enforced and that session management follows best practices.

Description

Improper neutralization of input in Nagvis before version 1.9.47 which can lead to XSS

References

Community reviews

Loading reviews…