dbcve.org
ItopApplication · Combodo

CVE-2024-51994

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-07
Fix available
A fix is available. Upgrade to 2.7.11 / 3.1.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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. In affected versions uploading a text file containing some java script in the portal will trigger an Cross-site Scripting (XSS) vulnerability. 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 stored Cross-Site Scripting (XSS) vulnerability in the portal component. An authenticated or unauthenticated attacker can upload a text file containing malicious JavaScript code, which gets executed when other users view or access the uploaded file, potentially leading to session hijacking, credential theft, or other client-side attacks.

MitigationUpgrade to iTop version 3.2.0 or later to address this vulnerability. No workaround is available.

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.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 (typically at /env-production/combodo-itop-version.php or check the iTop welcome page/header for version display). Compare the version number against the affected ranges: versions < 2.7.11 or >= 3.0.0 but < 3.1.2 are vulnerable.
    Affected if The installed version falls outside the fixed releases (3.1.2 and above, or 2.7.11 and above within the 2.x branch).
  2. Confirm portal component is accessible
    Check if the iTop portal is accessible by navigating to the portal URL (typically /pages/portal.php or similar). Verify whether the portal endpoint responds and does not return a 403/404 error.
    Affected if The portal is accessible and functional, exposing the file upload functionality to users.
  3. Determine if anonymous portal access is enabled
    Review the iTop configuration file (production-config.php or config-itop.php) for the 'portal' section and check the 'allow_anonymous' or 'anonymous_users' setting. Alternatively, test the portal login page to see if registration or guest access is permitted.
    Affected if Anonymous/unauthenticated users can access the portal or register themselves, enabling the upload vector without credentials.

You are affected if your iTop version is < 2.7.11 or >= 3.0.0 but < 3.1.2 AND the portal component with file upload capability is accessible to at least some 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.1.2 or later
Fixed in 2.7.113.1.2
Interim mitigation

Upgrade to iTop version 3.2.0 or later to address this vulnerability. No workaround is available.

Recommended fix High confidence

iTop 3.2.0

  1. Download iTop version 3.2.0 from the official Combodo download repository
  2. Review the iTop upgrade documentation for your current version
  3. Create a complete backup of your iTop database and files
  4. Put your iTop instance into maintenance mode if applicable
  5. Extract and deploy the new version 3.2.0 files to your web server
  6. Run the iTop upgrade wizard/console to update the database schema
  7. Verify the installation by logging into the application
  8. Confirm the text file upload functionality works correctly without executing injected scripts
Caveat Review release notes for 3.0.0-3.2.0 for potential breaking changes in configuration, extensions, or customizations

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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