dbcve.org
ItopApplication · Combodo

CVE-2025-24026

MEDIUM · 5.3 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 3.2.1 or later.
See remediation →
59/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. Versions prior to 3.2.1 are vulnerable to regular expression denial of service (ReDoS) that may, under some circumstances, affect iTop server. Version 3.2.1 doesn't use the affected variable in the regular expression. As a workaround, if iTop app_root_url is defined in the configuration file, then there is no possible way to exploit this ReDoS.

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

iTop versions prior to 3.2.1 contain a regular expression denial of service (ReDoS) vulnerability. The issue stems from an affected variable being used within a regex pattern that can be triggered by specially crafted input, potentially causing excessive CPU consumption on the iTop server.

MitigationUpgrade to iTop version 3.2.1 or later, or alternatively define the app_root_url parameter in the configuration file as a workaround to prevent exploitation of this ReDoS vulnerability.

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

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/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 installed iTop version
    Locate the iTop configuration file (typically config.php or env-productionconfig.php in the iTop web root) and check for a version indicator, or look for a VERSION file in the iTop installation directory. Alternatively, access the iTop setup/wizard page which often displays version information.
    Affected if The installed version is any release prior to 3.2.1 (e.g., 3.2.0, 3.1.x, 3.0.x, or earlier)
  2. Locate iTop configuration file
    Navigate to the iTop web root directory and identify the active configuration file - commonly config.php or the environment-specific configuration in the /conf directory.
    Affected if You cannot locate a valid iTop configuration file in the expected locations
  3. Check if app_root_url parameter is defined
    Open the active iTop configuration file and search for the parameter 'app_root_url'. This parameter is typically defined within the 'app_root_url' key in the configuration array.
    Affected if The app_root_url parameter is NOT defined in the configuration file (the parameter is absent or commented out)

You are affected if your iTop version is prior to 3.2.1 AND the app_root_url parameter is not defined in your configuration file, as this combination allows the vulnerable regex pattern to be triggered by specially crafted input.

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.1 or later
Fixed in 3.2.1
Interim mitigation

Upgrade to iTop version 3.2.1 or later, or alternatively define the app_root_url parameter in the configuration file as a workaround to prevent exploitation of this ReDoS vulnerability.

Recommended fix Moderate confidence

iTop 3.2.1

  1. 1. Back up your iTop installation directory and database before proceeding
  2. 2. Download iTop version 3.2.1 from the official GitHub repository or distribution channel
  3. 3. Extract the new version files to your web server
  4. 4. Run the iTop upgrade process following standard upgrade procedures
  5. 5. Verify that iTop is functioning correctly after the upgrade
  6. 6. Confirm the app_root_url is properly configured in the configuration file

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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