CVE-2021-26024
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 Favorites component before 1.0.2 for Nagios XI 5.8.0 is vulnerable to Insecure Direct Object Reference: it is possible to create favorites for any other user account.
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 confidenceThe Favorites component in Nagios XI 5.8.0 before version 1.0.2 contains an Insecure Direct Object Reference (IDOR) vulnerability that allows authenticated users to create favorites for arbitrary user accounts by manipulating object references, bypassing proper authorization checks on the favorites resource.
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< 1.0.2CVSS 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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Identify if Nagios XI is installedRun command 'rpm -qa | grep -i nagios' or check for Nagios XI installation directories such as /usr/local/nagiosxi/Affected if Nagios XI is present on the system
-
Locate the Nagios Favorites componentCheck the Nagios XI components directory for the favorites component, typically found within the Nagios XI installation under html/includes/components/ or query via the Nagios XI admin interface under 'System Profile' > 'Components'Affected if The Favorites component directory or entry exists in Nagios XI
-
Determine the installed Favorites component versionView the version information in the favorites component files (such as version.php or component_info.xml) or access the component details through the Nagios XI administrative interface under 'System Profile' > 'Components' > 'Favorites'Affected if The installed version is lower than 1.0.2 (e.g., 1.0.1, 1.0.0, or older)
-
Verify if the Favorites feature is accessibleLog in to Nagios XI as an authenticated user and navigate to a page that uses the Favorites component, or examine if the favorites functionality is loaded in the web interfaceAffected if The Favorites feature is enabled and accessible to authenticated users
A user is affected if Nagios XI with the Favorites component version 1.0.1 or lower is installed and the Favorites feature is accessible to authenticated users.
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.
From vendor data1.0.2
Upgrade the Nagios XI Favorites component to version 1.0.2 or later which includes proper authorization validation. If immediate patching is not possible, implement access controls at the application layer to validate that the authenticated user owns the target favorite resource.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26024 — 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-26024 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