Skip to main content
VulnerabilityPublished Updated

CVE-2026-30890: Combodo iTop · Cross-site Scripting

Affects Combodo iTopSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.0 High : upgrade to 3.2.3 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade iTop and combodo/iTop to 3.2.3.

Affected software

ProductAffectedFixed in
CombodoiTopAffected
  • <3.2.3
Fixed in
  • 3.2.3
GitHubcombodo/iToppkg:github/combodo/iTopOther threatsAffected
  • <3.2.3
Fixed in
  • 3.2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Combodo iTop version 3.2.3 or later, where this reflected XSS vulnerability has been fixed. No other mitigation is required as the vendor has provided an official fix.

Description

Combodo iTop versions prior to 3.2.3 contain a reflected Cross-Site Scripting (XSS) vulnerability in the synchro import script. This vulnerability allows improper neutralization of input during web page generation, potentially enabling an attacker to execute arbitrary scripts in the context of the affected application. The issue has been fixed in version 3.2.3.

References

Community reviews

Loading reviews…