CVE-2023-40931 is an SQL injection vulnerability affecting Nagios XI from version 5.11.0 through 5.11.1. The flaw is present in the administrative endpoint banner_message-ajaxhelper.php, where the ID parameter in a POST request is not properly sanitized before being incorporated into SQL queries. An authenticated attacker can exploit this weakness to execute arbitrary SQL commands against the application's backend database. Depending on database permissions and application context, exploitation can expose or alter stored application data and may facilitate further compromise of the Nagios XI instance.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a Proof of Concept (PoC) exploit for CVE-2023-40931, targeting Nagios XI. The main exploit script (exploit.py) authenticates to the Nagios XI web interface, obtains an authentication token, and tests for SQL injection in the 'banner_message-ajaxhelper.php' endpoint. It can optionally invoke sqlmap to automate database extraction. The admin-exploit.py script attempts to create a new admin user via the Nagios XI API and execute a reverse shell, though the reverse shell functionality is noted as unreliable. The repository includes detailed usage instructions and example payloads in the readme.md. The exploit demonstrates the ability to exploit SQL injection vulnerabilities and, if successful, could allow an attacker to extract sensitive data or gain administrative access. The code is written in Python and is intended for educational and authorized testing purposes only.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.