CVE-2025-47932
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 · uneditedCombodo 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 rendered via an AJAX call. Versions 2.7.13 and 3.2.2 sanitize the var responsible for the attack.
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 confidenceCombodo iTop versions prior to 2.7.13 and 3.2.2 contain a stored cross-site scripting (XSS) vulnerability in the dashboard rendering component when called via AJAX. The vulnerable variable is not properly sanitized before being rendered in the web page, allowing an authenticated attacker to inject malicious JavaScript that executes in other users' browser sessions.
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< 2.7.13>= 3.0.0, < 3.2.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed iTop versionLocate the version file or admin interface: check the version.txt file in the iTop root directory, or log into the iTop admin console and navigate to the version information page. Compare the version number against the affected ranges: < 2.7.13 or >= 3.0.0 and < 3.2.2Affected if The installed version is less than 2.7.13, or is 3.0.0 through 3.2.1 (inclusive)
-
Confirm AJAX dashboard functionality is accessibleCheck if the dashboard feature is enabled and accessible via web browser. Attempt to access a dashboard page via AJAX request (typically URLs containing /ajax/dashboard/ or similar endpoint patterns). Verify the application responds to dashboard-related AJAX callsAffected if AJAX dashboard endpoints are reachable and the application responds to them without authentication errors
-
Review dashboard configuration for user-created contentInspect the iTop database or dashboard configuration files for any user-defined dashboard entries. Use database queries to look for recent or suspicious dashboard configurations if you have database access. Check for any dashboard definitions that may contain unexpected script tags or encoded JavaScriptAffected if The application stores custom dashboard definitions in the database and these entries can contain unsanitized user input
-
Check authentication settings for dashboard accessReview iTop authentication configuration to determine if lower-privileged users can create or modify dashboards. Verify which user roles have permission to create or edit dashboard content, as the CVE requires an authenticated attackerAffected if Users with limited privileges (non-admin) can access dashboard creation or editing features
You are affected if your iTop version falls within the vulnerable range (< 2.7.13 or >= 3.0.0 and < 3.2.2) AND the dashboard AJAX functionality is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.7.133.2.2
Upgrade iTop to version 2.7.13 or 3.2.2 or later, which includes proper sanitization of the dashboard variable. Alternatively, disable or restrict dashboard functionality via AJAX until the upgrade can be applied.
Upgrade to iTop 2.7.13+ (for 2.x users) or iTop 3.2.2+ (for 3.x users)
- Identify the currently installed iTop version by checking the application or configuration files
- If running iTop 2.x version < 2.7.13, plan an upgrade to version 2.7.13 or the latest 2.x stable release
- If running iTop 3.x version >= 3.0.0 and < 3.2.2, plan an upgrade to version 3.2.2 or the latest 3.x stable release
- Review the release notes for your target version to check for any breaking changes or migration requirements
- Perform a full backup of the iTop database and configuration files before upgrading
- Execute the upgrade following the official iTop upgrade documentation
- After upgrade, verify the dashboard AJAX rendering works correctly and the XSS vulnerability is patched
- Confirm the new version number matches the expected fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47932 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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