CVE-2020-11696
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 · uneditedIn Combodo iTop a menu shortcut name can be exploited with a stored XSS payload. This is fixed in all iTop packages (community, essential, professional) in version 2.7.0 and iTop essential and iTop professional in version 2.6.4.
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 confidenceA stored (persistent) XSS vulnerability exists in Combodo iTop where malicious JavaScript code can be injected through menu shortcut names. When users view the affected menu, the injected payload executes in their 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< 2.6.4< 2.7.0CVSS 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.
-
Check installed iTop versionAccess the iTop admin interface and navigate to the version information page, or check the version file in the iTop installation directory. Compare the version number to the affected ranges: < 2.6.4 or < 2.7.0Affected if The installed version is lower than 2.6.4 or is between 2.6.4 and 2.7.0 (exclusive)
-
Verify menu shortcuts feature is in useCheck if the iTop installation has any custom menu shortcuts configured. This can be done by accessing the menu customization section in the iTop admin console or by querying the database for entries in tables related to menu configurationAffected if Menu shortcuts feature is enabled and has custom shortcuts configured
-
Inspect menu shortcut entries for malicious contentQuery the database for menu shortcut name entries. Look for shortcut names containing HTML tags, JavaScript code, or unusual character sequences that could indicate injected payloads (e.g., <script>, javascript:, onerror=, onload=)Affected if Any menu shortcut name contains executable script content or suspicious HTML/JavaScript patterns
-
Review recent menu modification historyCheck the application or database logs for recent changes to menu shortcuts. Look for entries created or modified around the time the vulnerability could have been exploitedAffected if There are unexpected or unauthorized menu shortcut modifications in the audit log
The environment is affected if the installed iTop version is below 2.6.4 or between 2.6.4 and 2.7.0, AND the menu shortcuts feature contains injected malicious code in shortcut name fields.
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.6.42.7.0
Upgrade iTop to version 2.7.0 or later (or 2.6.4 for essential/professional editions). Audit existing menu shortcuts for malicious content and implement input validation for menu shortcut names.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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-2020-11696 — 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-2020-11696 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