CVE-2021-37350
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNagios XI before version 5.8.5 is vulnerable to SQL injection vulnerability in Bulk Modifications Tool due to improper input sanitisation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNagios XI versions before 5.8.5 contain a SQL injection vulnerability in the Bulk Modifications Tool due to improper input sanitization. Attackers can inject malicious SQL queries through user-supplied input in this component, potentially enabling unauthorized database access, data exfiltration, or complete system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 5.8.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Nagios XI is installedLook for Nagios XI processes running on the system or check for Nagios XI installation directories (commonly /usr/local/nagiosxi or /opt/nagiosxi).Affected if Nagios XI software is present on the system.
-
Determine installed Nagios XI versionAccess the Nagios XI web interface and navigate to Admin > System Info, or run the command: cat /usr/local/nagiosxi/etc/packageinfo.json (path may vary based on installation).Affected if The installed version is lower than 5.8.5 (e.g., 5.8.0, 5.7.x, etc.).
-
Verify Bulk Modifications Tool is accessibleLog into the Nagios XI web interface and check if the Bulk Modifications Tool is available under the Tools menu or at /nagiosxi/tools.php?type=bulk_mod (path may vary).Affected if The Bulk Modifications Tool component is enabled and accessible to the user.
-
Check if user-supplied input is accepted by Bulk Modifications ToolExamine the Bulk Modifications Tool functionality - look for input fields that accept user data (e.g., host names, service descriptions, or template parameters) that could be used to inject SQL queries.Affected if The Bulk Modifications Tool accepts user input without evident input validation or uses the input in database queries.
A system is affected if Nagios XI version is below 5.8.5 and the Bulk Modifications Tool component is accessible and accepts user-supplied input.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.8.5
Upgrade to Nagios XI version 5.8.5 or later which includes proper input validation and parameterized queries to remediate the SQL injection vulnerability.
5.8.5 or later (latest stable release)
- Upgrade Nagios XI to version 5.8.5 or later
- Verify the upgrade by checking the Nagios XI version in the web interface under 'Admin' > 'System Information'
- After upgrade, confirm the Bulk Modifications Tool functions correctly
- Review Nagios XI release notes for any additional security patches included
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37350 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data