dbcve.org
Nagios XiApplication · Nagios

CVE-2013-10074

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 2012 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 2012R2.6 are vulnerable to cross-site scripting (XSS) via the Tools Menu of the web interface. Insufficient validation or escaping of user-supplied input may allow an attacker to inject and execute arbitrary script in the context of a victim's browser.

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

Nagios XI versions prior to 2012R2.6 contain a stored cross-site scripting (XSS) vulnerability in the Tools Menu section of the web interface. The application fails to properly validate or escape user-supplied input, allowing authenticated attackers to inject malicious JavaScript that executes in the context of other users' browsers.

MitigationUpgrade Nagios XI to version 2012R2.6 or later. Alternatively, implement proper input validation and output encoding on all Tools Menu parameters and review similar input fields throughout the application for comparable vulnerabilities.

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:< 2012= 2012= 2012r1.6= 2012r1.7= 2012r1.8= 2012r1.9= 2012r2.0= 2012r2.1= 2012r2.2= 2012r2.3= 2012r2.4= 2012r2.5

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Nagios XI version
    Locate the version information in the Nagios XI web interface under 'Admin' > 'System Information' > 'General' or check the version file at /usr/local/nagiosxi/etc/constants.php
    Affected if The installed version is 2012R2.5 or earlier, or matches any of the affected version strings: 2012, 2012r1.6, 2012r1.7, 2012r1.8, 2012r1.9, 2012r2.0, 2012r2.1, 2012r2.2, 2012r2.3, 2012r2.4, or 2012r2.5
  2. Verify Tools Menu is accessible
    Log into the Nagios XI web interface as an authenticated user and navigate to the Tools Menu section in the main navigation
    Affected if The Tools Menu section is present and accessible to authenticated users in the web interface
  3. Confirm user authentication is required
    Verify that the Nagios XI web interface requires user login. Attempt to access the Tools Menu without logging in or check authentication configuration in the Nagios XI admin panel under 'General' > 'System Settings' > 'Login Settings'
    Affected if The application allows authenticated users to access the Tools Menu, as the vulnerability is exploitable by authenticated attackers

If the installed Nagios XI version is 2012R2.5 or earlier and the Tools Menu is accessible to authenticated users, the environment is affected by this stored XSS vulnerability.

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 2012 or later
Fixed in 2012
Interim mitigation

Upgrade Nagios XI to version 2012R2.6 or later. Alternatively, implement proper input validation and output encoding on all Tools Menu parameters and review similar input fields throughout the application for comparable vulnerabilities.

Recommended fix High confidence

Nagios XI 2012R2.6 or later

  1. Back up the current Nagios XI installation, including configuration files and database
  2. Verify current Nagios XI version by navigating to Admin > System Information in the web interface
  3. Download Nagios XI 2012R2.6 or later from the official Nagios website (www.nagios.com)
  4. Run the upgrade script as root: ./upgrade.sh or use the web-based upgrade from Admin > System Management > System Upgrade
  5. Follow the on-screen prompts to complete the upgrade process
  6. Verify the upgrade was successful by checking the version in Admin > System Information
  7. Test that the Tools Menu functions properly after upgrade
  8. Clear browser cache and verify the XSS vulnerability is no longer present in the Tools Menu
Caveat Review Nagios XI 2012R2.6 release notes for any configuration changes or plugin compatibility notes before upgrading

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-10074 — 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-2013-10074 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