dbcve.org
ItopApplication · Combodo

CVE-2024-52002

HIGH · 8.8 CVSS v3.1 Published 2024-11-08
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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. Several url endpoints are subject to a Cross-Site Request Forgery (CSRF) vulnerability. Please refer to the linked GHSA for the complete list. This issue has been addressed in version 3.2.0 and 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 contains a Cross-Site Request Forgery (CSRF) vulnerability affecting multiple URL endpoints. Attackers can exploit this by tricking authenticated users into submitting malicious requests to those endpoints, potentially performing unauthorized actions within the application.

MitigationUpgrade to iTop version 3.2.0. No workarounds exist; the vulnerable endpoints must be updated to the patched version.

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:< 3.2.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 iTop installation version
    Access the iTop administrator interface and navigate to the 'About' or 'Version' section typically found in the admin dashboard or help menu. Alternatively, locate the version file in the iTop installation directory (commonly named version.php, datamodel.xml, or similar).
    Affected if The displayed version number is lower than 3.2.0 (e.g., 3.1.x, 3.0.x, 2.x series)
  2. Check version in configuration files
    Open the iTop configuration file (often named config.php or similar in the root installation folder) and look for a version parameter or constant that displays the installed iTop release number.
    Affected if The configuration file reports a version below 3.2.0
  3. Compare installed version to CVE scope
    Review the identified version number against the affected range specified in the CVE: all versions of Combodo iTop prior to version 3.2.0 are vulnerable.
    Affected if The installed version is any release prior to 3.2.0, including 3.1.0, 3.1.1, 3.1.2, and earlier major versions
  4. Confirm iTop is actively in use
    Verify that the iTop instance is a production or development system that processes authenticated user sessions, as the CSRF vulnerability requires authenticated users to be targeted.
    Affected if iTop is deployed and active with user authentication enabled, combined with a version below 3.2.0

The environment is affected if the installed Combodo iTop version is any release prior to 3.2.0.

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 3.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade to iTop version 3.2.0. No workarounds exist; the vulnerable endpoints must be updated to the patched version.

Recommended fix High confidence

3.2.0

  1. Create a complete backup of the iTop database and all application files
  2. Download iTop version 3.2.0 from the official source (e.g., GitHub releases or official download page)
  3. Stop the web server to prevent access during the upgrade process
  4. Replace the existing iTop files with the new version 3.2.0 files
  5. Run the iTop upgrade script or navigate to the setup/upgrade page in a web browser to complete the database migration
  6. Restart the web server
  7. Verify the installation by logging in and testing core functionality
  8. Confirm the version number displays as 3.2.0

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

Fix this in Itop Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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