Security readout for executives and security teams
Plain-English summary
Older versions of Nagios XI, a popular IT monitoring platform, contain a flaw in the Core Config Manager screens used to edit monitored objects. A logged-in user with access to those pages could trick the database into running unintended commands, potentially exposing or altering monitoring configuration and stored data. Upgrading to Nagios XI 5.7.4 or later removes the issue.
Executive priority
Patch on the next available maintenance window if Nagios XI is in use; treat as urgent if the instance is internet-facing or shares credentials with other systems. Business risk is elevated because monitoring tooling often holds privileged credentials and broad network reach, so a compromise can cascade into wider operational impact.
Technical view
Multiple SQL injection flaws (CWE-89) exist in the Core Config Manager (CCM) object edit pages in Nagios XI prior to 5.7.4 / CCM 3.0.7. User-supplied parameters are concatenated into SQL queries without proper sanitization. An authenticated user with CCM access can inject SQL to read or modify configuration and application data. CVSS 4.0 base score is 8.7 (AV:N/AC:L/PR:L/UI:N/VC:H/VI:H/VA:H), reflecting high impact on confidentiality, integrity, and availability of the application.
Likely exposure
Internet-exposed Nagios XI instances on versions earlier than 5.7.4 with CCM enabled are most at risk, particularly where low-privileged accounts can reach object edit pages. Internal-only deployments still face risk from any authenticated user, contractor, or compromised credential. Organizations that have updated to 5.7.4 or newer should be unaffected.
Exploitation context
Public sources do not flag active in-the-wild exploitation, and the CVE is not listed in CISA KEV. The flaw requires an authenticated CCM user, which lowers the bar for insider abuse or attackers who already harvested credentials. VulnCheck and the Nagios change log corroborate the existence of the bug; treat any unpatched, reachable instance as a plausible attack path rather than a hypothetical one.
Researcher notes
Issue is post-authentication SQLi in CCM object edit pages, fixed in CCM 3.0.7 / Nagios XI 5.7.4. CWE-89, CVSS 4.0 8.7. No public KEV listing or confirmed mass exploitation in the cited sources. The CVE record was published in 2025 for a fix shipped in the 5.7.4 line, so version inventories should be cross-checked against the Nagios change log rather than CVE publish date alone. VulnCheck advisory is the primary third-party reference.
Mitigation direction
- Upgrade Nagios XI to 5.7.4 or later (CCM 3.0.7+) per the vendor change log.
- Restrict CCM access to a small set of trusted administrators while patching is scheduled.
- Remove Nagios XI from direct internet exposure and place it behind VPN or zero-trust access.
- Rotate Nagios XI account passwords and any database credentials accessible from the host after upgrade.
- Review vendor advisories for any additional CCM hardening guidance before re-enabling broad access.
Validation and detection
- Confirm the running Nagios XI version from the admin UI or /etc/xi-version and verify it is 5.7.4 or later.
- Check the CCM component version and ensure it is 3.0.7 or newer.
- Audit Nagios XI access logs for unusual CCM object edit activity by low-privileged users.
- Review the Nagios database for unexpected configuration changes or unfamiliar accounts.
- Validate that CCM endpoints are not reachable from untrusted networks via external scanning.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupDatabase 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 lookupCVE-2020-36859 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://www.nagios.com/changelog/nagios-xi/CVE reference · release-notes, patch
- https://www.vulncheck.com/advisories/nagios-xi-ccm-sqli-via-object-edit-pagesCVE reference · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.