CVE-2025-27139
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.12, 3.1.2, and 3.2.0 are vulnerable to cross-site scripting when the preferences page is opened. Versions 2.7.12, 3.1.2, and 3.2.0 fix the issue.
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.12, 3.1.2, and 3.2.0 contain a stored cross-site scripting (XSS) vulnerability in the user preferences page. An attacker with access to the preferences functionality could inject malicious JavaScript that executes when other users view the preferences page.
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.12>= 3.0.0, < 3.1.2= 3.2.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 iTop versionLocate the version file or check the application administration interface for the installed iTop version number. Common locations include a version.php file in the main directory or the admin/overview page.Affected if The installed version is prior to 2.7.12, or is 3.0.0 through 3.1.1, or equals 3.2.0
-
Verify preferences functionality is accessibleConfirm that regular users or attackers can access the user preferences or profile settings page within the iTop application.Affected if User preferences functionality is enabled and accessible to non-admin users
-
Inspect user preference fields for injected scriptsExamine the database table that stores user preferences (typically the pref* table or user preferences storage) or view the preferences page directly to identify any unexpected script tags, event handlers, or javascript: URIs in preference values.Affected if Any preference field contains unsanitized HTML or JavaScript code that would execute when the preferences page is viewed by other users
A user is affected if they run an iTop version in the vulnerable range AND the preferences page is accessible to users who could inject malicious scripts, or if malicious scripts already exist in preference storage.
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.123.1.2
Upgrade iTop to version 2.7.12, 3.1.2, or 3.2.0 or later to patch the XSS vulnerability in the preferences page.
Upgrade to iTop 2.7.12 (for 2.x users), 3.1.2 (for 3.0.x users), or 3.2.0 (for 3.2.0 users)
- Backup the current iTop installation and database before proceeding with the upgrade
- Identify your current version branch (2.x or 3.x) to determine which fixed release to upgrade to
- For iTop 2.x users (< 2.7.12): Download iTop version 2.7.12 from the official source
- For iTop 3.0.x users (>= 3.0.0, < 3.1.2): Download iTop version 3.1.2 from the official source
- For iTop 3.2.0 users: Download iTop version 3.2.0 from the official source
- Follow the standard iTop upgrade procedure: stop web server, replace application files, run the upgrade wizard, restart web server
- Verify the preferences page loads correctly and the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27139 — 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-27139 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