dbcve.org
ItopApplication · Combodo

CVE-2025-64167

MEDIUM · 6.1 CVSS v3.1 Published 2025-11-10
Fix available
A fix is available. Upgrade to 2.7.13 / 3.2.2 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 web based IT service management tool. Versions prior to 2.7.13 and 3.2.2 are vulnerable to a cross-site scripting attack (leading to JS execution) when editing the URL parameter. Versions 2.7.13 and 3.2.2 don't use export.php, which was deprecated. They use export-v2.php instead.

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 versions prior to 2.7.13 and 3.2.2 contain a reflected cross-site scripting (XSS) vulnerability in the deprecated export.php component. Attackers can manipulate URL parameters to inject malicious JavaScript that executes in victim browsers when they access crafted links.

MitigationUpgrade iTop to version 2.7.13 or 3.2.2 or later, which replaces the vulnerable export.php with the newer export-v2.php component.

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.13>= 3.0.0, < 3.2.2

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 installed iTop version
    Locate the version file in your iTop installation directory (commonly in /version.php or /core/version.php) and read the version number.
    Affected if The version is less than 2.7.13, or greater than or equal to 3.0.0 but less than 3.2.2.
  2. Locate the deprecated export.php file
    Search for export.php in the web root or known application directories of your iTop installation.
    Affected if The file export.php exists in your iTop installation.
  3. Verify if the legacy export module is active
    Check your iTop configuration files (such as config.php or module configuration) for any settings that enable or load the deprecated export functionality.
    Affected if The deprecated export module or component is enabled in the configuration.
  4. Confirm the newer export-v2.php exists
    Search for export-v2.php in the same directory where export.php was found.
    Affected if The newer export-v2.php file does NOT exist, indicating the installation has not been patched to the fixed version.

Your environment is affected if your installed iTop version falls below 2.7.13 or between 3.0.0 and 3.2.2, and the deprecated export.php file is present and accessible on your server.

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.13 / 3.2.2 or later
Fixed in 2.7.133.2.2
Interim mitigation

Upgrade iTop to version 2.7.13 or 3.2.2 or later, which replaces the vulnerable export.php with the newer export-v2.php component.

Recommended fix High confidence

iTop 2.7.13 (for 2.x branch) or iTop 3.2.2 (for 3.x branch)

  1. 1. Identify which major version branch you are currently running (2.x or 3.x)
  2. 2. For users on iTop 2.x versions: upgrade to version 2.7.13 or later
  3. 3. For users on iTop 3.x versions: upgrade to version 3.2.2 or later
  4. 4. After upgrading, verify that the deprecated export.php is no longer in use and that export-v2.php is functioning properly
  5. 5. Test that XSS protection is working correctly in the export functionality
  6. 6. Consider reviewing application logs for any signs of exploitation attempts prior to patching
Caveat Review the relevant release notes for your version branch to check for any breaking changes between your current version and the target fixed version

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

Fix this in Itop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64167 — 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-2025-64167 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