dbcve.org
ItopApplication · Combodo

CVE-2024-51740

HIGH · 8.8 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 2.7.11 / 3.0.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Combodo iTop is a simple, web based IT Service Management tool. This vulnerability can be used to create HTTP requests on behalf of the server, from a low privileged user. The user portal form manager has been fixed to only instantiate classes derived from it. This issue has been addressed in versions 2.7.11, 3.0.5, 3.1.2, and 3.2.0. 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

This is a class instantiation vulnerability in Combodo iTop's user portal form manager. A low-privileged user could instantiate arbitrary classes (not just those derived from the expected base class), enabling HTTP requests to be made on behalf of the server (Server-Side Request Forgery). The fix restricts instantiation to only classes properly derived from the form manager base class.

MitigationUpgrade to version 2.7.11, 3.0.5, 3.1.2, or 3.2.0. No workarounds are available; immediate patching is required given the CVSS 8.8 severity and low-privileged user exploitation vector.

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.11>= 3.0.0, < 3.0.5>= 3.1.0, < 3.1.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 installed version
    Locate the version file or check the application admin interface for the current iTop version. Common locations include a version.php file in the root directory or the Version field in the admin dashboard.
    Affected if The installed version is less than 2.7.11, or falls between 3.0.0 and 3.0.4 inclusive, or falls between 3.1.0 and 3.1.1 inclusive.
  2. Verify portal module is enabled
    Check the iTop configuration for the portal module status. Look for portal-related configuration entries in the main configuration file or the module administration page.
    Affected if The portal feature is enabled and accessible to users.
  3. Confirm portal form manager is active
    Examine the application modules list or configuration to verify that the user portal form manager component is loaded and functional.
    Affected if The portal form manager module is active in the installation.
  4. Check user access controls on portal
    Review the user roles and profiles assigned to standard users to determine if low-privileged users have portal access permissions.
    Affected if Standard or low-privileged users have the ability to access and interact with the portal forms.

The environment is affected if the installed iTop version is within any of the vulnerable ranges AND the user portal with form manager functionality is enabled and accessible to low-privileged users.

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.11 / 3.0.5 / 3.1.2 or later
Fixed in 2.7.113.0.53.1.2
Interim mitigation

Upgrade to version 2.7.11, 3.0.5, 3.1.2, or 3.2.0. No workarounds are available; immediate patching is required given the CVSS 8.8 severity and low-privileged user exploitation vector.

Recommended fix High confidence

Upgrade to iTop 3.2.0 (or at minimum 2.7.11, 3.0.5, or 3.1.2 depending on your current major version line)

  1. Backup the iTop installation directory and database before proceeding with any upgrade
  2. Download the fixed version (3.2.0 recommended as the latest stable release) from the official Combodo iTop repository or distribution channel
  3. Follow the official iTop upgrade documentation to apply the update
  4. After upgrading, verify the fix by checking that the user portal form manager only instantiates classes derived from it
  5. Confirm the iTop application is functioning correctly and test that the SSRF vulnerability is no longer exploitable
Caveat Review iTop release notes for migration considerations between major versions; test in a non-production environment first

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

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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