Nagios XiApplication · Nagios

CVE-2024-13993

MEDIUM · 6.1 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2024 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
Nagios XI versions prior to < 2024R1.1.2 are vulnerable to a reflected cross-site scripting (XSS) via the login page when accessed with older web browsers. Insufficient validation or escaping of user-supplied input reflected by the login page can allow an attacker to craft a malicious link that, when visited by a victim, executes arbitrary JavaScript in the victim’s browser within the Nagios XI origin. The issue is observable under legacy browser behaviors; modern browsers may mitigate some vectors.

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 · high confidence

Nagios XI versions prior to 2024R1.1.2 contain a reflected cross-site scripting (XSS) vulnerability in the login page. User-supplied input is insufficiently validated or escaped before being reflected in the login page response, allowing attackers to craft malicious URLs that execute arbitrary JavaScript in victims' browsers within the Nagios XI origin when visited.

MitigationUpgrade Nagios XI to version 2024R1.1.2 or later to address the insufficient input validation in the login page. Users should avoid clicking untrusted links to the Nagios XI login page.

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
Nagios XiApplication
Affected:< 2024= 2024

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 the installed Nagios XI version
    Access the Nagios XI administration interface and navigate to the version information page, or use the version check command in the system terminal if available
    Affected if The displayed version is earlier than 2024R1.1.2 or shows as exactly version 2024
  2. Verify the login page is accessible
    Confirm that the Nagios XI login page is reachable via web browser at your installation URL
    Affected if The login page is exposed and the version check shows a vulnerable version
  3. Confirm the vulnerability scope
    The vulnerability exists in the login page where user-supplied input is reflected back without proper validation
    Affected if You are running Nagios XI version 2024 or any version prior to 2024R1.1.2 and the login page is accessible

A user is affected if their Nagios XI installation shows a version earlier than 2024R1.1.2 or exactly version 2024 and the login page 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 2024 or later
Fixed in 2024
Interim mitigation

Upgrade Nagios XI to version 2024R1.1.2 or later to address the insufficient input validation in the login page. Users should avoid clicking untrusted links to the Nagios XI login page.

Recommended fix High confidence

2024R1.1.2

  1. Back up the current Nagios XI installation and database before proceeding with the upgrade
  2. Download Nagios XI version 2024R1.1.2 from the official Nagios website (www.nagios.com)
  3. Run the Nagios XI upgrade script or use the web-based upgrade interface to install version 2024R1.1.2
  4. Verify the upgrade was successful by checking the Nagios XI version in the web interface
  5. Test that the login page functions correctly and the XSS vulnerability is no longer present

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-13993 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