CVE-2021-47694
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.4 / Nagios XI 5.8.6 contains a reflected cross-site scripting (XSS) vulnerability via the Test Command functionality. Insufficient validation or escaping of user-supplied input may allow an attacker to inject and execute arbitrary script in the context of a victim's browser.
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 confidenceReflected cross-site scripting (XSS) vulnerability in Nagios XI Core Config Manager (CCM) Test Command functionality. Insufficient validation or escaping of user-supplied input allows injection and execution of arbitrary JavaScript in victim's browser context.
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.6CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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.
-
Verify Nagios XI installation existsCheck for Nagios XI directory: ls /usr/local/nagiosxi/ or look for Nagios XI web files in the webrootAffected if If the directory or web files exist, Nagios XI is installed on this system
-
Determine installed Nagios XI versionRun: cat /usr/local/nagiosxi/etc/version.ini or access the web interface and go to Admin > System Info to view the version numberAffected if If the version shown is below 5.8.6, the installation falls within the affected version range
-
Confirm CCM module is accessibleAccess the Core Config Manager via the web interface at /nagiosxi/ccm/ or check if CCM appears in the main navigation menuAffected if If CCM is accessible, the Test Command functionality is available and could be exploited
-
Verify Test Command feature is presentIn the CCM web interface, navigate to the Commands section and look for a Test Command option or buttonAffected if If the Test Command feature exists and is accessible, the XSS vulnerability can be triggered
The environment is affected if Nagios XI version is below 5.8.6 AND the CCM Test Command functionality is accessible and enabled
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.6
Upgrade to Nagios XI CCM 3.1.4 / Nagios XI 5.8.6 or later which contains proper input validation and output encoding fixes for the Test Command functionality.
Nagios XI 5.8.6 (or later)
- 1. Back up your current Nagios XI installation and database before upgrading
- 2. Download Nagios XI version 5.8.6 or later from the official Nagios website (www.nagios.com)
- 3. Follow Nagios official upgrade documentation to apply the update
- 4. Verify the upgrade was successful by checking the Nagios XI version in the web interface
- 5. Test the Core Config Manager Test Command functionality to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-47694 — 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-47694 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