dbcve.org
ItopApplication · Combodo

CVE-2024-52601

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 2.7.12 / 3.1.3 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
iTop is an web based IT Service Management tool. Prior to versions 2.7.12, 3.1.3, and 3.2.1, anyone with an account having portal access can have read access to objects they're not allowed to see by querying an unprotected route. Versions 2.7.12, 3.1.3, and 3.2.1 contain a fix for the issue.

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 · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in iTop's web API. Users with portal access can bypass authorization checks by querying an unprotected route, allowing them to read sensitive objects they're not permitted to access.

MitigationUpgrade iTop to version 2.7.12, 3.1.3, or 3.2.1 which contain the access control fix. Alternatively, restrict portal access to trusted users only until the upgrade can be applied.

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.12>= 3.0.0, < 3.1.3>= 3.2.0, < 3.2.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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
    Check the version.php file in your iTop root directory, or look for the version number in the iTop administration console (usually displayed on the welcome page or in the About section)
    Affected if The installed version is less than 2.7.12, or between 3.0.0-3.1.2 inclusive, or between 3.2.0-3.2.0 inclusive
  2. Confirm portal access is enabled
    Check if the /pages/ or /portal/ endpoint is accessible and functional in your iTop installation. Look for portal-related configuration files such as conf/production.combodo.itop.portal.php or similar portal configuration in your config directory
    Affected if Portal access is enabled and exposed to users
  3. Verify API endpoint exposure
    Test whether the web API endpoints are reachable without proper authorization by attempting to access objects via the API that you know you should not have access to, or review web server logs for unusual API access patterns from portal users
    Affected if Unprotected API routes are accessible to portal users who should not have access to certain objects

You are affected if your iTop version falls within the vulnerable ranges AND the portal is accessible to users who should not have access to all objects in the system.

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.12 / 3.1.3 / 3.2.1 or later
Fixed in 2.7.123.1.33.2.1
Interim mitigation

Upgrade iTop to version 2.7.12, 3.1.3, or 3.2.1 which contain the access control fix. Alternatively, restrict portal access to trusted users only until the upgrade can be applied.

Recommended fix High confidence

Upgrade to 2.7.12 (for 2.x branch), 3.1.3 (for 3.0.x branch), or 3.2.1 (for 3.2.x branch) - choose the appropriate version matching your current branch

  1. Identify the currently installed iTop version by checking the application or configuration files
  2. Determine which version branch you are on (2.x, 3.0.x, or 3.2.x)
  3. Backup the iTop database and application files before upgrading
  4. For iTop 2.x versions: upgrade to version 2.7.12 or later
  5. For iTop 3.0.x versions: upgrade to version 3.1.3 or later
  6. For iTop 3.2.x versions: upgrade to version 3.2.1 or later
  7. Follow the standard iTop upgrade documentation for your version branch
  8. Verify the upgrade was successful by logging in and testing access controls

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

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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