CVE-2021-37352
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 · uneditedAn open redirect vulnerability exists in Nagios XI before version 5.8.5 that could lead to spoofing. To exploit the vulnerability, an attacker could send a link that has a specially crafted URL and convince the user to click the link.
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 · moderate confidenceAn open redirect vulnerability in Nagios XI before version 5.8.5 allows attackers to craft malicious URLs containing specially crafted redirect parameters that can forward users to arbitrary external websites, enabling phishing and spoofing attacks.
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
- 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.
-
Confirm Nagios XI is installedCheck if the Nagios XI web interface is accessible by accessing the server hostname or IP via HTTP/HTTPS in a browser, or verify the Nagios XI service is running using system commands like 'systemctl status nagiosxi' or checking for nagios-related processesAffected if Nagios XI is not installed or not accessible
-
Identify the installed Nagios XI versionLog into the Nagios XI web interface and navigate to the Admin > System Information page, or use the command line: run '/usr/local/nagiosxi/scripts/get_version.sh' or check '/usr/local/nagiosxi/etc/version.ini'Affected if Unable to retrieve version information
-
Compare version against affected rangeCheck if the installed version number is less than 5.8.5 (e.g., 5.8.0, 5.7.5, 5.6.0, etc.)Affected if Installed version is < 5.8.5 (any version like 5.8.4, 5.8.3, 5.7.x, 5.6.x, or earlier)
-
Assess web interface exposureDetermine if the Nagios XI web interface is reachable over the network on HTTP/HTTPS ports (typically 80/443 or 8080/8443)Affected if The web interface is externally accessible without proper network segmentation
If Nagios XI is installed and the installed version is confirmed to be less than 5.8.5, the environment is affected by this open redirect vulnerability.
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 Nagios XI to version 5.8.5 or later to obtain the vendor patch; alternatively, implement URL validation and allowlist controls on redirect parameters in the web application.
Nagios Xi 5.8.5 or later
- Verify current Nagios Xi version by checking the Nagios Xi administration interface or running the appropriate version check command
- Download Nagios Xi version 5.8.5 or later from the official Nagios website (www.nagios.com)
- Follow the official Nagios Xi upgrade documentation to apply the upgrade
- After upgrade, verify the version has been successfully updated to 5.8.5 or later
- Test that the open redirect vulnerability is no longer present by attempting to access a URL with a redirect parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37352 — 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-37352 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