CVE-2021-21407
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 · uneditedCombodo iTop is an open source, web based IT Service Management tool. Prior to version 2.7.4, the CSRF token validation can be bypassed through iTop portal via a tricky browser procedure. The vulnerability is patched in version 2.7.4 and 3.0.0.
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 confidenceCombodo iTop versions prior to 2.7.4 contain a CSRF token validation bypass vulnerability in the web portal. An attacker can exploit this by leveraging a tricky browser procedure to bypass the anti-CSRF token checks, potentially allowing unauthorized state-changing actions to be performed on behalf of authenticated users.
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< 2.7.4CVSS 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
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 the installed iTop versionLocate the iTop installation directory and check the version file (commonly version.php or similar release metadata file). Typical paths include /var/www/html/itop/ or the web root where iTop is installed. Look for a file that contains the version string.Affected if The version number found is less than 2.7.4 (for example, 2.7.0, 2.6.x, 2.5.x, etc.)
-
Confirm the web portal is enabledCheck the iTop configuration file (typically config.php or the datamodel XML files) for the portal module settings. Look for entries related to the portal application or web portal feature.Affected if The portal feature is installed and enabled in the configuration.
-
Verify user authentication is possible in the portalAttempt to access the portal login page at the standard portal URL path (commonly /itop/portal/ or /pages/portal.php). Confirm the login form is accessible and functional.Affected if The portal login page loads and accepts authentication credentials, meaning users can log in.
-
Check for CSRF token implementationExamine the portal source code or HTTP responses when performing actions in the portal. Look for the presence and handling of CSRF tokens in form submissions and AJAX requests.Affected if The portal does not properly validate CSRF tokens on state-changing actions (this requires code review or penetration testing to confirm the bypass is exploitable).
You are affected if you are running any iTop version below 2.7.4 AND the web portal is enabled and accessible for user authentication, as the CSRF token validation bypass applies specifically to authenticated portal sessions.
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 data2.7.4
Upgrade iTop to version 2.7.4 or 3.0.0 or later to obtain the patched code that properly validates CSRF tokens in the portal interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21407 — 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-21407 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