dbcve.org
ItopApplication · Combodo

CVE-2023-34445

MEDIUM · 6.1 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 2.7.9 / 3.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Combodo iTop is a simple, web based IT Service Management tool. When displaying pages/ajax.render.php XSS are possible for scripts outside of script tags. This issue 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 confidence

Combodo iTop is vulnerable to cross-site scripting (XSS) in the pages/ajax.render.php endpoint. The vulnerability allows attackers to inject malicious scripts outside of proper script tags when the application renders pages, potentially enabling session hijacking or credential theft via malicious JavaScript execution in victim browsers.

MitigationUpgrade iTop to version 2.7.9, 3.0.4, 3.1.0 or later to patch the XSS vulnerability. No workarounds exist; immediate upgrade is required.

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
ItopApplication
Affected:< 2.7.9>= 3.0.0, < 3.0.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed iTop version
    Check the iTop version by accessing the admin dashboard (usually at /itop/pages/UI.php?c=menu&menu=admin) or look for a version.php file in the installation directory that contains the version string
    Affected if The installed version is less than 2.7.9 OR greater than or equal to 3.0.0 but less than 3.0.4
  2. Confirm the ajax.render.php endpoint exists
    Verify that the file pages/ajax.render.php is present in your iTop web root directory
    Affected if The file exists and is accessible, indicating a potentially vulnerable installation
  3. Check application accessibility
    Verify that the iTop web interface is publicly or externally accessible via HTTP/HTTPS
    Affected if The application is network-accessible to untrusted users, enabling them to reach the vulnerable endpoint

You are affected if your iTop installation version is either below 2.7.9 or falls within the 3.0.0 to 3.0.3 range, and the web interface is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.7.9 / 3.0.4 or later
Fixed in 2.7.93.0.4
Interim mitigation

Upgrade iTop to version 2.7.9, 3.0.4, 3.1.0 or later to patch the XSS vulnerability. No workarounds exist; immediate upgrade is required.

Recommended fix High confidence

Upgrade to iTop version 2.7.9, 3.0.4, or 3.1.0 (choose the appropriate version based on your current release branch)

  1. 1. Backup the current iTop installation directory and database before upgrading
  2. 2. Identify the currently installed iTop version to determine the appropriate upgrade path
  3. 3. Download the fixed version from the official Combodo iTop repository or distribution channel
  4. 4. For iTop versions < 2.7.9: upgrade to version 2.7.9
  5. 5. For iTop versions >= 3.0.0 and < 3.0.4: upgrade to version 3.0.4 or 3.1.0
  6. 6. Extract the new version files to replace the existing installation
  7. 7. Run the iTop setup/upgrade wizard to update the database schema
  8. 8. Verify the installation by accessing the web interface and testing the pages/ajax.render.php functionality
Caveat Review release notes for version-specific changes; upgrading across major version branches (e.g., 2.x to 3.x) may require testing

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34445 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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