dbcve.org
ItopApplication · Combodo

CVE-2025-48065

MEDIUM · 6.1 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 →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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. Versions prior to 2.7.13 and 3.2.2 are vulnerable to cross-site scripting when a field with an error contains malicious content. Versions 2.7.13 and 3.2.2 protect rendered HTML content.

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 contain a stored cross-site scripting (XSS) vulnerability in the form field error handling mechanism. When validation fails on user-supplied input, the error message renders the unsanitized content back to the browser, allowing injection of malicious HTML or JavaScript.

MitigationUpgrade iTop to version 2.7.13 or 3.2.2 or later, which implements proper HTML encoding for rendered content in error messages.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 at /datamodel/lastchange.log or check the iTop admin dashboard under the 'About' or 'Configuration' section for the exact version number
    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. Verify PHP version
    Run `php -v` from command line or check via phpinfo() to confirm PHP is installed (the vulnerability is in iTop but requires a running PHP environment)
    Affected if PHP is present and iTop version falls in vulnerable range - this confirms the application stack exists
  3. Locate form handling code
    Inspect the /core/formvalidator.class.php file or similar form validation logic in the iTop installation directory to confirm the error rendering mechanism exists
    Affected if The form validation and error handling code is present in the installation - this is where the unsanitized output occurs
  4. Identify user-facing input forms
    Review custom or extended XML data models in the /data/models directory or any custom extensions that define user-input fields (text inputs, textareas)
    Affected if User-supplied input fields are defined in the iTop data model - these could trigger the XSS when validation fails
  5. Check for custom error message templates
    Examine templates in /templates/ or /pages/ directories for any custom error message rendering logic that might override default behavior
    Affected if Custom templates exist that handle form validation errors - this confirms the error output path exists in the environment

A user is affected if their installed iTop version is below 2.7.13 or between 3.0.0 and 3.2.2, and they have forms accepting user input that would display error messages upon validation failure.

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 iTop to version 2.7.13 or 3.2.2 or later, which implements proper HTML encoding for rendered content in error messages.

Recommended fix High confidence

iTop 2.7.13 (for 2.x branch) or 3.2.2 (for 3.x branch)

  1. 1. Identify the currently installed iTop version (check version file or admin interface)
  2. 2. If running version < 2.7.13, plan upgrade to version 2.7.13
  3. 3. If running version >= 3.0.0 and < 3.2.2, plan upgrade to version 3.2.2
  4. 4. Before upgrading, create a full backup of the iTop database and configuration files
  5. 5. Download the appropriate fixed version from the official iTop source (github.com/Combodo/iTop)
  6. 6. Follow the standard iTop upgrade procedure: extract the new version, preserve the configuration file, run the web-based setup/upgrade wizard
  7. 7. Complete the upgrade and verify successful installation
  8. 8. Confirm the XSS fix is working by testing that error messages with HTML/script content are properly escaped

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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