dbcve.org
Nagios XiApplication · Nagios

CVE-2023-40931

MEDIUM · 6.5 CVSS v3.1 Published 2023-09-19
Fix available
A fix is available. Upgrade to 5.11.2 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
A SQL injection vulnerability in Nagios XI from version 5.11.0 up to and including 5.11.1 allows authenticated attackers to execute arbitrary SQL commands via the ID parameter in the POST request to /nagiosxi/admin/banner_message-ajaxhelper.php

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

SQL injection vulnerability in Nagios XI allows authenticated attackers to execute arbitrary SQL commands through the ID parameter in POST requests to /nagiosxi/admin/banner_message-ajaxhelper.php. The lack of proper input sanitization or parameterized queries in the affected component enables attackers to inject malicious SQL syntax.

MitigationApply vendor patches for Nagios XI 5.11.0-5.11.1 or upgrade to a patched version. Implement input validation and parameterized queries as immediate compensating controls if patching is delayed.

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:>= 5.11.0, < 5.11.2

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. Identify Nagios XI installation
    Locate the Nagios XI web directory (commonly /usr/local/nagiosxi/htdocs/ or /var/www/html/nagiosxi/) or check for the Nagios XI web interface response at your server URL.
    Affected if Nagios XI is installed on the server.
  2. Determine installed Nagios XI version
    Check the version file typically found in the Nagios XI directory, or access the Nagios XI admin interface and look for the version displayed in the footer or About page.
    Affected if The version is 5.11.0 or 5.11.1.
  3. Verify vulnerable component exists
    Confirm the file /nagiosxi/admin/banner_message-ajaxhelper.php exists in the Nagios XI web directory.
    Affected if The file exists on the system.
  4. Confirm authentication requirement context
    Determine whether user accounts with access to /nagiosxi/admin/ exist and whether they can submit POST requests to the vulnerable endpoint.
    Affected if Authenticated admin users can access the affected endpoint.

If Nagios XI version 5.11.0 or 5.11.1 is installed and the banner_message-ajaxhelper.php file exists, the environment is affected by this SQL injection vulnerability when an authenticated attacker can access the admin interface.

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

Apply vendor patches for Nagios XI 5.11.0-5.11.1 or upgrade to a patched version. Implement input validation and parameterized queries as immediate compensating controls if patching is delayed.

Recommended fix High confidence

Nagios XI 5.11.2

  1. 1. Back up the current Nagios XI installation and database before proceeding with any upgrade.
  2. 2. Download Nagios XI version 5.11.2 or later from the official Nagios website (www.nagios.com).
  3. 3. Run the Nagios XI upgrade script or use the web-based upgrade interface to install version 5.11.2.
  4. 4. After upgrade, verify the /nagiosxi/admin/banner_message-ajaxhelper.php endpoint is updated and no longer vulnerable.
  5. 5. Confirm the upgrade was successful by logging in and checking the Nagios XI version in the admin interface.

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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