CVE-2023-47399: Nagios XI Audit Log Integrity Weakness via Excessive Database Privileges
CVE-2023-47399 affects Nagios XI and allows the Nagios XI database user (nagiosxi) to update or delete records in the xi_auditlog table. Based on the provided advisory context, the issue is not a memory corruption or code execution flaw but an authorization and integrity weakness in database privilege design: the application database account was granted full CRUD capabilities over audit log records when audit data should be append-only or otherwise protected from modification and deletion. This undermines the trustworthiness of Nagios XI audit logging because actions recorded for administrative and security-relevant events can be altered or removed by an attacker who gains the ability to act through that database user or abuse application functionality that uses it.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
The primary impact is loss of forensic integrity and reduced detectability of malicious activity. An attacker who obtains access equivalent to the nagiosxi database user can delete or modify audit log entries in xi_auditlog, making it significantly easier to conceal unauthorized actions, impede incident response, and frustrate post-compromise investigation. The vulnerability weakens accountability and non-repudiation within Nagios XI and can support follow-on objectives such as persistence, privilege abuse, and anti-forensics by removing evidence of attacker activity.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, review and harden MySQL/MariaDB grants for the nagiosxi database user to remove unnecessary UPDATE and DELETE permissions on xi_auditlog, provided this does not break required application behavior. Monitor for unexpected modifications or deletions of audit records, enable external log forwarding or immutable centralized logging so audit events are preserved outside the local application database, and restrict access to database credentials and administrative application functions that could expose or leverage the database account. Regular integrity checks and backups of audit data can also reduce anti-forensic impact.
Remediation
Patch, then assume compromise.
Upgrade Nagios XI to version 5.11.4 or later, as the provided advisory states that all disclosed vulnerabilities, including CVE-2023-47399, were mitigated in Nagios XI 5.11.4. In addition, database permissions for the application account should be restricted according to least privilege so that audit log data cannot be updated or deleted by the standard application database user unless strictly required by a controlled maintenance path. Audit records should be made append-only where feasible, and privilege assignments on the xi_auditlog table should be reviewed and reduced.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2023-47399 exploited in the wild?
- As of Jun 9, 2026, Mallory has no reports of CVE-2023-47399 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2023-47399?
- As of Jun 9, 2026, Mallory has found no public exploit for CVE-2023-47399.
- Is there a patch for CVE-2023-47399?
- Upgrade Nagios XI to version 5.11.4 or later, as the provided advisory states that all disclosed vulnerabilities, including CVE-2023-47399, were mitigated in Nagios XI 5.11.4. In addition, database permissions for the application account should be restricted according to least privilege so that audit log data cannot be updated or deleted by the standard application database user unless strictly required by a controlled maintenance path.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.