dbcve.org
ItopApplication · Combodo

CVE-2025-47286

HIGH · 7.2 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 →
78/100
Remediation priority · High
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, an administrator can, by editing the configuration of the iTop instance, execute code on the server. Versions 2.7.13 and 3.2.2 escape and check the config parameter before executing a command based on it.

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 versions prior to 2.7.13 and 3.2.2 allow an administrator to execute arbitrary code on the server by editing the iTop configuration. The vulnerability stems from insufficient validation of configuration parameters before they are used in command execution. Versions 2.7.13 and 3.2.2 address this by escaping and validating config parameters prior to command execution.

MitigationUpgrade to iTop version 2.7.13 or 3.2.2 or later, which properly escapes and validates configuration parameters before executing commands based on them.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 installed iTop version
    Locate the version file or check the configuration file for version information. Typical locations include a version.php file or the main config file in the application root directory.
    Affected if The version is less than 2.7.13 or greater than or equal to 3.0.0 but less than 3.2.2
  2. Locate iTop configuration file
    Find the main iTop configuration file, typically named config.php or similar in the application root or conf directory.
    Affected if The configuration file exists and is writable by the web server user
  3. Check for command execution configuration parameters
    Examine the configuration file for parameters that control external command execution, such as paths to executables, backup commands, or any parameter used in shell execution functions.
    Affected if The configuration contains parameters that are used in system command execution without proper validation
  4. Verify administrator access to configuration
    Confirm whether the current environment allows administrators to edit the iTop configuration through the web interface or direct file access.
    Affected if Administrator accounts can modify the configuration file directly

A user is affected if their iTop installation version is below 2.7.13 or between 3.0.0 and 3.2.2 (exclusive), AND administrators have the ability to modify configuration parameters that get used in command execution.

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 or later, which properly escapes and validates configuration parameters before executing commands based on them.

Recommended fix High confidence

Upgrade to iTop 2.7.13 (for 2.x versions) or iTop 3.2.2 (for 3.x versions), or a later stable release if available

  1. Backup the iTop installation directory and database before proceeding
  2. Download the appropriate fixed version: iTop 2.7.13 (for 2.x line) or iTop 3.2.2 (for 3.x line) from the official Combodo download area
  3. Verify the integrity of the downloaded package using checksums if provided
  4. Put the iTop application in maintenance mode if available, or temporarily restrict access
  5. Extract and deploy the new version files, overwriting existing files while preserving the conf/production.cnf configuration file
  6. Run the iTop setup/upgrade process via the web interface or command line to apply any database migrations
  7. Clear any caches (删除 datamodels/ and data/cache/ directories if they exist)
  8. Verify the upgrade was successful by logging in and checking the iTop version
Caveat Review the iTop release notes for the target version to check for any breaking changes or required migration steps 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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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