dbcve.org
NagvisApplication

CVE-2024-47090

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-27
Fix available
A fix is available. Upgrade to 1.9.47 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-site scripting (XSS) vulnerability in Nagvis versions prior to 1.9.47 due to improper neutralization of user-supplied input. The application fails to properly sanitize input before rendering it in web pages, allowing attackers to inject malicious scripts that execute in the context of other users' browsers.

MitigationUpgrade to Nagvis version 1.9.47 or later to receive the patch for this XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NagvisApplication
Affected:< 1.9.47

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nagvis installation
    Locate the Nagvis installation directory or access the web interface footer which typically displays the version number
    Affected if Cannot determine version from installation or web interface
  2. Check installed Nagvis version
    Inspect the version file (often version.php or similar in the Nagvis directory) or view the version displayed in the web interface
    Affected if Version number is lower than 1.9.47 (e.g., 1.9.46, 1.9.40, etc.)
  3. Confirm web interface is accessible
    Verify that the Nagvis web interface is accessible to users or external systems
    Affected if Web interface is exposed and version is below 1.9.47

Environment is affected if the installed Nagvis version is below 1.9.47 and the web interface is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.9.47 or later
Fixed in 1.9.47
Interim mitigation

Upgrade to Nagvis version 1.9.47 or later to receive the patch for this XSS vulnerability.

Recommended fix Moderate confidence

1.9.47

  1. 1. Back up your current Nagvis installation and configuration
  2. 2. Download Nagvis version 1.9.47 or later from the official Nagvis repository (www.nagvis.org)
  3. 3. Extract the new version to your Nagvis installation directory
  4. 4. Run the upgrade process following standard Nagvis upgrade procedures
  5. 5. Verify the upgrade was successful by accessing the Nagvis web interface
  6. 6. Test that the XSS vulnerability is no longer present by validating input handling in affected areas

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nagvis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-47090 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data