Skip to main content
Mallory
UnratedVulnerability

CVE-2023-47400: RCE in Nagios XI Custom Includes

Updated 5 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-47400CWE-434

CVE-2023-47400 is a high-severity remote code execution vulnerability in the Nagios XI Custom Includes feature affecting Nagios XI v5.11.1. According to the provided context, the protection model for Custom Includes could be bypassed by overwriting or removing the .htaccess file that was intended to prevent execution of uploaded content, and then uploading a PHP payload disguised with an allowed filename or extension pattern such as "exploit.jpg.php". Once the uploaded file was reachable over the web interface, the attacker could request it directly and cause the embedded PHP code to execute on the Nagios XI server. The issue is therefore an unrestricted or insufficiently restricted file upload condition combined with ineffective server-side execution controls in the upload location.

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.

Successful exploitation allows remote code execution on the Nagios XI server in the context of the web application. An attacker can upload and execute arbitrary PHP code, which can be used to run system commands, access application data, modify configuration, establish persistence, and potentially pivot further within the monitored environment depending on the privileges and local configuration of the Nagios XI host.

Mitigation

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

If immediate patching is not possible, restrict access to the Custom Includes functionality to the smallest possible administrative set, disable or tightly control file upload capability in that feature, and enforce web-server rules that categorically prevent script execution from upload directories regardless of application-managed .htaccess content. Additional compensating controls include monitoring for unexpected .php files in Custom Includes paths, detecting changes to .htaccess files, and limiting direct web access to administrative interfaces through network ACLs or reverse-proxy restrictions. Specific temporary mitigations beyond these general measures are not provided in the source content.

Remediation

Patch, then assume compromise.

Upgrade Nagios XI to version 5.11.4 or later. The provided context states that all 16 vulnerabilities in the advisory, including CVE-2023-47400, were mitigated in Nagios XI 5.11.4. Because the issue involves bypass of upload protections and execution controls, remediation should ensure both the application logic and web-server handling of uploaded Custom Includes content are corrected so uploaded files cannot overwrite protective .htaccess controls or be executed as PHP.

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-47400 exploited in the wild?
As of Jun 9, 2026, Mallory has no reports of CVE-2023-47400 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2023-47400?
As of Jun 9, 2026, Mallory has found no public exploit for CVE-2023-47400.
Is there a patch for CVE-2023-47400?
Upgrade Nagios XI to version 5.11.4 or later. The provided context states that all 16 vulnerabilities in the advisory, including CVE-2023-47400, were mitigated in Nagios XI 5.11.4.
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.