LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15050: Nagios XI < 5.2.4 SQL Injection in Notification Search

Nagios XI versions prior to 5.2.4 contain a SQL injection vulnerability in the notification search functionality. User-supplied search parameters were incorporated into SQL statements without adequate parameterization or sanitation, allowing an authenticated user to manipulate database queries. Successful exploitation could disclose or modify notification data and, in some cases, impact the application database more broadly.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in older Nagios XI monitoring software (before version 5.2.4) lets a logged-in user trick the notification search feature into running unintended database commands. An attacker with valid credentials could read or change monitoring data, and potentially reach more of the underlying database. Upgrading to 5.2.4 or later resolves the issue.

Executive priority

Treat as a high-priority patching item for any Nagios XI deployment older than 5.2.4. Authenticated SQL injection in a monitoring platform can expose sensitive operational data and accelerate lateral movement, so confirm version status quickly.

Technical view

CVE-2016-15050 is a CWE-89 SQL injection in the Nagios XI notification search functionality affecting versions prior to 5.2.4. User-supplied search parameters reach SQL statements without sufficient parameterization, allowing an authenticated user to manipulate queries, disclose or alter notification records, and potentially affect broader database content. CVSS 4.0 base 8.7 (AV:N/AC:L/PR:L).

Likely exposure

Organizations running Nagios XI versions older than 5.2.4 with any authenticated user access to the notification search feature. Internet-exposed Nagios XI portals or shared monitoring tenants increase exposure; isolated, fully patched 5.2.4+ deployments are not affected.

Exploitation context

No active exploitation is cited and the CVE is not on CISA KEV. Exploitation requires an authenticated session, but Nagios XI installs frequently use shared or weakly protected credentials, lowering the practical barrier for a determined insider or credential-thief.

Researcher notes

CWE-89 SQL injection in the notification search endpoint of Nagios XI prior to 5.2.4. CVSS 4.0 base 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) reflects authenticated network access with high confidentiality, integrity, and availability impact on the vulnerable component. No public PoC, KEV entry, or exploitation telemetry is cited in the source bundle; VulnCheck advisory and Nagios changelog are the primary references. Affected version data in the bundle is sparse (defaultStatus "unaffected" with version "0"); rely on the vendor changelog to confirm fixed build 5.2.4. Validate by inventorying Nagios XI versions and reviewing application/database logs for anomalous queries originating from the notification search workflow.

Mitigation direction

  • Upgrade Nagios XI to version 5.2.4 or later per vendor changelog.
  • Restrict Nagios XI web access to trusted networks or VPN until patched.
  • Enforce strong, unique credentials and disable unused or shared accounts.
  • Review and tighten role permissions for users with notification access.
  • Place a WAF or reverse proxy in front of Nagios XI to flag SQLi patterns.
  • Consult Nagios vendor guidance for any additional hotfix or hardening steps.

Validation and detection

  • Inventory Nagios XI hosts and confirm running version against 5.2.4 baseline.
  • Review web and database logs for unusual notification search query patterns.
  • Audit Nagios XI user accounts and recent authentication events for misuse.
  • Test the patched build in a staging environment before production rollout.
  • Verify upgrade success by re-checking version and running vendor health checks.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-15050 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2016-15050Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NagiosXI0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.