CVE-2023-34443
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 a simple, web based IT Service Management tool. When displaying page Run queries Cross-site Scripting (XSS) are possible for scripts outside of script tags. This has been fixed in versions 2.7.9, 3.0.4, 3.1.0. All users are advised to upgrade. There are no known workarounds for this vulnerability.
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 confidenceCombodo iTop contains a stored Cross-site Scripting (XSS) vulnerability in the 'Run queries' page where malicious scripts can be injected and executed outside of script tags. This allows attackers to embed malicious JavaScript that executes in the browsers of users viewing the affected page.
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.9>= 3.0.0, < 3.0.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
- 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.
-
Identify installed iTop versionLocate the version file or check the application footer/admin page for the exact version number of Combodo iTopAffected if The version is below 2.7.9, or between 3.0.0 and 3.0.4 inclusive
-
Confirm Run queries feature is accessibleNavigate to or check if the 'Run queries' page is present in the iTop web interface (typically under the Queries or Data menu)Affected if The Run queries page exists and is accessible to the user being assessed
-
Verify query execution capabilityCheck if the logged-in user has permissions to create or modify queries in the Run queries interfaceAffected if Users with query creation/modification privileges can access this feature
-
Inspect stored query definitionsExamine the database tables (such as priv_query or similar) or the Run queries page for any unexpected or suspicious query names or values that may contain script tags or HTML attributesAffected if Any query entries contain unsanitized user input that could execute as JavaScript
You are affected if your iTop version is below 2.7.9 or between 3.0.0-3.0.4 AND the Run queries feature is accessible to users in your environment.
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 · scoped2.7.93.0.4
Upgrade iTop to version 2.7.9, 3.0.4, or 3.1.0 to patch the XSS vulnerability. No workarounds are available.
iTop 2.7.9 (for 2.x users) or iTop 3.0.4/3.1.0 (for 3.x users)
- Determine your current iTop version by checking the application's login page or configuration
- If running iTop 2.x (version < 2.7.9), upgrade to version 2.7.9 or later (e.g., 2.7.9)
- If running iTop 3.0.x (version >= 3.0.0 and < 3.0.4), upgrade to version 3.0.4 or later (recommended: 3.1.0)
- If running a version earlier than 3.0.0 on a different major line, upgrade to the latest stable release (3.1.0)
- Before upgrading, backup your iTop database and configuration files
- Follow the standard iTop upgrade procedure: extract the new version, copy your configuration file, and run the setup/upgrade wizard
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-2023-34443 — 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-2023-34443 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