CVE-2021-47693
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 · uneditedThe Core Config Manager (CCM) in Nagios XI versions prior to CCM 3.1.3 / Nagios XI 5.8.5 contains a SQL injection vulnerability in the search text handling. Unsanitized user-supplied input was incorporated into SQL queries used by configuration object editors, allowing authenticated users to inject SQL fragments. Successful exploitation could lead to unauthorized disclosure or modification of configuration and application data, and in some environments could allow further compromise of the application or backend database.
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 confidenceSQL injection vulnerability in Nagios XI's Core Config Manager (CCM) allows authenticated users to inject malicious SQL fragments through unsanitized search text input that gets incorporated into configuration object editor queries, potentially exposing or modifying application data.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Nagios XI versionLog into the Nagios XI web interface as administrator and navigate to the 'About' page (typically Admin > System Information) to view the installed version number. Alternatively, check the RPM package with command 'rpm -qa | grep nagiosxi' or review the file /usr/local/nagiosxi/etc/includes/version.ini if it exists.Affected if Installed version is below 5.8.5
-
Confirm Core Config Manager is enabledVerify the Core Config Manager (CCM) interface is accessible. Log into Nagios XI and attempt to access the CCM by navigating to 'Configure' > 'Core Config Manager' or the /nagiosxi/ccm/ path. Check if the CCM module is listed as enabled in Admin > System Information > System Modules.Affected if CCM is installed and accessible via the web interface
-
Verify user authentication is enabledConfirm that Nagios XI user authentication is active. Check that at least one user account exists in Admin > User Management and that the web interface requires login. The SQL injection requires an authenticated user session.Affected if User authentication is configured and CCM is reachable without additional network restrictions
Environment is affected if Nagios XI version is below 5.8.5, Core Config Manager is accessible, and authenticated users can access the CCM search functionality.
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
Update to Nagios XI CCM 3.1.3 / XI 5.8.5 or later to obtain the patched version; alternatively, implement proper input sanitization and parameterized queries in the affected CCM search handlers.
Nagios XI 5.8.5 (or later) / CCM 3.1.3
- 1. Back up the current Nagios XI installation and database before proceeding with any upgrade.
- 2. Download Nagios XI 5.8.5 or later from the official Nagios website (www.nagios.com).
- 3. Run the Nagios XI upgrade installer following the official upgrade documentation.
- 4. Verify the upgrade was successful by logging into the Nagios XI interface.
- 5. Confirm the Core Config Manager (CCM) version shows 3.1.3 or later after upgrade.
- 6. Test that the previously vulnerable search functionality in CCM is working correctly after the fix.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-47693 — 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-47693 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