Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2018-10735: SQL Injection in Nagios XI admin/commandline.php

Published May 16, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.2High · v3
EPSS41.7%99th percentile
CISA KEVNoNot listed
In the wildReported23 exploitation records in Mallory
Vendor
Nagios Enterprises
IdentifiersCVE-2018-10735CWE-89 · Improper Neutralization of Special…

Nagios XI before version 5.4.13 contains a SQL injection vulnerability in the admin/commandline.php script, specifically in the handling of the 'cname' parameter. Unsanitized user input in this parameter is directly incorporated into SQL queries, allowing attackers to manipulate the database through crafted requests.

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 an authenticated attacker to execute arbitrary SQL commands against the Nagios XI database. This can lead to data leakage, data modification, or potentially full compromise of the application depending on the database privileges of the web application.

Mitigation

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

Restrict access to the admin/commandline.php endpoint to trusted users only, and employ web application firewalls (WAFs) to detect and block SQL injection attempts as an interim measure until the application is patched.

Remediation

Patch, then assume compromise.

Upgrade to Nagios XI version 5.4.13 or later, where proper input validation and parameterized queries are implemented to prevent SQL injection via the 'cname' parameter in admin/commandline.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.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Nagios EnterprisesNagios Xiapplication
FAQ

Frequently asked questions

Is CVE-2018-10735 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2018-10735?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2018-10735.
Is there a patch for CVE-2018-10735?
Upgrade to Nagios XI version 5.4.13 or later, where proper input validation and parameterized queries are implemented to prevent SQL injection via the 'cname' parameter in admin/commandline.php.
What products are affected by CVE-2018-10735?
Nagios Enterprises Nagios Xi.
How severe is CVE-2018-10735?
CVE-2018-10735 has a CVSS v3 score of 7.2 (High) and an EPSS score of 41.7% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 signatures1YARA, 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.