dbcve.org
ItopApplication · Combodo

CVE-2025-47773

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 dashboard is edited via an AJAX call. 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 cross-site scripting (XSS) vulnerability in the dashboard editing functionality when processed via an AJAX call. The vulnerability allows injection of malicious scripts into rendered HTML content. The patched versions protect rendered HTML content to prevent XSS exploitation.

MitigationUpgrade iTop to version 2.7.13 or 3.2.2 (or later) to apply the fix that protects rendered HTML content from XSS attacks in the dashboard AJAX editing functionality.

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. Determine installed iTop version
    Locate the version file or check the application header/footer for the version number. Common locations include a version.php file in the main directory or the application login page footer.
    Affected if The version is below 2.7.13, or is 3.0.0 through 3.1.x, or is 3.2.0 or 3.2.1 (any version in the range < 2.7.13 or >= 3.0.0 and < 3.2.2).
  2. Verify dashboard module is enabled
    Log into iTop as an administrator and navigate to the Dashboard module. Check if the dashboard editing functionality is accessible via the user interface.
    Affected if The dashboard module is present and the AJAX-based dashboard editor is accessible to users.
  3. Identify AJAX endpoint for dashboard editing
    Inspect network traffic when accessing the dashboard editor. Look for AJAX requests to endpoints related to dashboard rendering or editing (typically in the pages/ajax or similar directory).
    Affected if AJAX endpoints handling dashboard content are reachable without additional authentication beyond standard iTop login.
  4. Check for absence of HTML encoding in dashboard responses
    Use browser developer tools or a proxy to capture AJAX responses from the dashboard editor. Examine the response content to see if HTML characters are being rendered without proper encoding.
    Affected if Raw HTML or unescaped script tags appear in the AJAX response content when dashboard widgets are rendered.

You are affected if your iTop version falls within the vulnerable ranges (< 2.7.13 or >= 3.0.0 and < 3.2.2) AND the dashboard editing feature is accessible to users who can trigger the AJAX-based dashboard rendering.

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) to apply the fix that protects rendered HTML content from XSS attacks in the dashboard AJAX editing functionality.

Recommended fix High confidence

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

  1. Identify your current iTop version (2.x or 3.x branch)
  2. Backup your iTop installation and database before upgrading
  3. For iTop 2.x users (< 2.7.13): Download and upgrade to version 2.7.13
  4. For iTop 3.x users (>= 3.0.0, < 3.2.2): Download and upgrade to version 3.2.2
  5. Follow the standard iTop upgrade procedure for your version
  6. Clear any caches after upgrade
  7. Verify the fix by testing dashboard editing via AJAX calls

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

Fix this in Itop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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