Skip to main content
Mallory
UnratedVulnerability

CVE-2023-47405: Weak Default MySQL Credentials in Nagios XI

Updated 6 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2023-47405CWE-1392

CVE-2023-47405 is a vulnerability in Nagios XI affecting at least version 5.11.1 in which the installer creates multiple MySQL database accounts with weak default credentials. According to the provided advisory context, a fresh installation creates at least three database users—nagiosxi, nagiosql, and ndoutils—using the password "n@gweb". This results in predictable, low-entropy credentials being present by default for backend database access.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

An attacker who can reach the MySQL service or otherwise obtain a path to authenticate with these database accounts may be able to log in using known default credentials and access Nagios XI backend data. Depending on the privileges assigned to those accounts and network exposure of MySQL, this could enable unauthorized reading or modification of monitoring data, configuration-related records, stored secrets in the database, or other application data, and may facilitate further compromise of the Nagios XI deployment.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, manually change the passwords for all Nagios XI-created MySQL users, restrict MySQL network exposure to trusted local interfaces or administrative hosts only, enforce host-based firewall controls, and audit applications and configuration files to ensure updated credentials are consistently used. Review database account privileges and reduce them to least privilege where possible.

Remediation

Patch, then assume compromise.

Upgrade Nagios XI to version 5.11.4 or later, as the advisory states that all listed vulnerabilities, including CVE-2023-47405, were mitigated in version 5.11.4. Additionally, rotate the passwords for the MySQL accounts created by Nagios XI, review their privileges, and ensure no deployments retain the default password "n@gweb" for the nagiosxi, nagiosql, or ndoutils users.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2023-47405 exploited in the wild?
As of Jun 9, 2026, Mallory has no reports of CVE-2023-47405 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-47405?
As of Jun 9, 2026, Mallory has found no public exploit for CVE-2023-47405.
Is there a patch for CVE-2023-47405?
Upgrade Nagios XI to version 5.11.4 or later, as the advisory states that all listed vulnerabilities, including CVE-2023-47405, were mitigated in version 5.11.4. Additionally, rotate the passwords for the MySQL accounts created by Nagios XI, review their privileges, and ensure no deployments retain the default password "n@gweb" for the nagiosxi, nagiosql, or ndoutils users.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.