dbcve.org
Nagios XiApplication · Nagios

CVE-2013-10072

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to after 2011 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 2012R1.6 contain an authorization flaw in the Auto-Discovery functionality. Users with read-only roles could directly reach Auto-Discovery endpoints and pages that should require elevated permissions, exposing discovery results and allowing unintended access to discovery operations.

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 before 2012R1.6 have an insecure direct object reference (IDOR) or broken access control vulnerability in the Auto-Discovery module. The application fails to properly enforce authorization checks, allowing authenticated users with read-only role permissions to directly access auto-discovery endpoints and pages that should require administrator or elevated privileges. This exposes sensitive network discovery results and permits unauthorized discovery operations.

MitigationUpgrade Nagios XI to version 2012R1.6 or later, which contains the fix for this authorization flaw. Additionally, review and enforce proper role-based access control (RBAC) settings to ensure read-only users cannot access administrative functions.

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:<= 2011= 2012

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Determine Nagios XI version
    Check the installed version by viewing the file /usr/local/nagiosxi/var/xi-sys.cfg or accessing the Nagios XI web interface Help > About page. Compare the version number against the affected ranges: versions <= 2011 or version 2012 (prior to 2012R1.6).
    Affected if The installed version is Nagios XI 2012 or earlier, specifically any version before 2012R1.6.
  2. Verify Auto-Discovery module status
    Check if the Auto-Discovery module is enabled by examining the Nagios XI configuration files in /usr/local/nagiosxi/etc/ or by reviewing the module status in the web interface under Admin > System Info > System Modules.
    Affected if The Auto-Discovery module is installed and enabled on the system.
  3. Review user role configuration
    Examine the user configuration database or the /usr/local/nagiosxi/etc/xi-users.inc.php file to identify users assigned the read-only role. Use the web interface under Admin > Users to list all users and their assigned roles.
    Affected if There exist user accounts configured with read-only role permissions in Nagios XI.
  4. Test access control on Auto-Discovery endpoints
    Log in as a read-only user account and attempt to access the Auto-Discovery functionality by navigating to the auto-discovery URLs directly (such as /nagiosxi/backend/?cmd=autodisc* endpoints) or by accessing the Auto-Discovery page in the web interface.
    Affected if A read-only user can successfully access auto-discovery pages, view discovery results, or trigger discovery operations without receiving an authorization error.

A user is affected if they run Nagios XI version 2012 or earlier, have the Auto-Discovery module enabled, and their read-only role users can access auto-discovery functionality that should require administrator privileges.

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 a release after 2011
Interim mitigation

Upgrade Nagios XI to version 2012R1.6 or later, which contains the fix for this authorization flaw. Additionally, review and enforce proper role-based access control (RBAC) settings to ensure read-only users cannot access administrative functions.

Recommended fix High confidence

2012R1.6

  1. Back up the current Nagios XI installation, configuration files, and database before starting the upgrade
  2. Download Nagios XI version 2012R1.6 from the official Nagios website (www.nagios.com)
  3. Run the Nagios XI upgrade installer following the official upgrade documentation
  4. After upgrade completion, verify the Auto-Discovery functionality now properly enforces authorization
  5. Confirm that read-only users can no longer access Auto-Discovery endpoints that require elevated permissions

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

Fix this in Nagios Xi Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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