dbcve.org
ItopApplication · Combodo

CVE-2025-49145

MEDIUM · 6.5 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 →
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
Combodo iTop is a web based IT service management tool. In versions prior to 2.7.13 and 3.2.2, a user that has enough rights to create webhooks (mostly administrators) can drop the database. This is fixed in iTop 2.7.13 and 3.2.2 by verifying callback signature.

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 an authenticated vulnerability in Combodo iTop where users with webhook creation privileges (typically administrators) can drop the database. The vulnerability exists in versions prior to 2.7.13 and 3.2.2 due to lack of callback signature verification, allowing malicious administrators to execute destructive database operations through the webhook functionality.

MitigationUpgrade to iTop version 2.7.13 or 3.2.2 which implements callback signature verification. Additionally, limit webhook creation permissions to only essential personnel and audit existing webhook configurations.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/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 the installed iTop version
    Locate the version number in the iTop installation - typically accessible through the iTop admin dashboard About page, or check version.php or similar version file in the installation directory. Compare your version against the affected ranges: versions < 2.7.13 or >= 3.0.0 and < 3.2.2 are vulnerable.
    Affected if Your installed version falls within < 2.7.13 or >= 3.0.0, < 3.2.2
  2. Verify the webhook module is present
    Check if the webhook functionality is available in your iTop installation. This is typically found as a module under the Webhooks section in the admin interface or in the list of enabled extensions/modules.
    Affected if The webhook module is installed and enabled in your environment
  3. Confirm webhook creation privileges exist
    Examine user profiles and permissions to determine which users or roles have the ability to create or modify webhooks. This is typically found in the User Profiles or Roles administration section under webhook-related permissions.
    Affected if Any user profile grants webhook creation or modification permissions (typically granted to Administrator profiles)
  4. Review existing webhook configurations
    Inspect the list of configured webhooks in the iTop admin interface. Look for any webhooks that may contain database operation callbacks, particularly those that could execute destructive commands.
    Affected if There are webhooks configured that invoke database-related callback actions

You are affected if your iTop version is vulnerable (< 2.7.13 or >= 3.0.0 and < 3.2.2) AND the webhook module is enabled AND users with webhook creation privileges exist in your environment.

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 to iTop version 2.7.13 or 3.2.2 which implements callback signature verification. Additionally, limit webhook creation permissions to only essential personnel and audit existing webhook configurations.

Recommended fix High confidence

Upgrade to iTop 2.7.13 (if on 2.x line) or iTop 3.2.2 (if on 3.x line)

  1. 1. Back up the iTop database and configuration files before proceeding with any upgrade.
  2. 2. Download the appropriate fixed version (2.7.13 for iTop 2.x or 3.2.2 for iTop 3.x) from the official Combodo GitHub repository or official distribution channel.
  3. 3. Place the application in maintenance mode if available, or temporarily restrict access.
  4. 4. Extract the new version files to replace the existing iTop installation, preserving the conf/config.php configuration file.
  5. 5. Run the iTop setup/upgrade process by accessing the setup page in a web browser.
  6. 6. Follow the on-screen upgrade wizard to complete the database schema migration.
  7. 7. After successful upgrade, verify that webhook functionality works correctly with the new signature verification.
  8. 8. Remove any temporary maintenance restrictions and restore normal access.
Caveat Review release notes for any configuration or behavioral changes between your current version and the target fixed version before upgrading.

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

Fix this in Itop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-2025-49145 — 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-49145 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