dbcve.org
ItopApplication · Combodo

CVE-2025-24969

MEDIUM · 5.0 CVSS v3.1 Published 2025-05-14
Fix available
A fix is available. Upgrade to 3.2.1 or later.
See remediation →
56/100
Remediation priority · Elevated
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
iTop is an web based IT Service Management tool. Prior to version 3.2.1, a portal user can see any other contacts picture by changing the picture ID in the URL. Version 3.2.1 contains a patch for 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 confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in iTop's portal. A user with portal access can view contact pictures belonging to other users by directly manipulating the picture ID parameter in the URL, bypassing proper authorization checks.

MitigationUpgrade iTop to version 3.2.1 or later, which contains the patch to enforce proper authorization before serving contact pictures.

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:< 3.2.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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
    Check your iTop installation's version number, typically found in the application admin interface under 'About' or 'System Information', or in a version file in the iTop root directory
    Affected if The installed version is lower than 3.2.1
  2. Confirm portal access is enabled
    Verify whether the iTop customer/portal interface is enabled in your configuration. Check the itop-config file or the portal settings to confirm the portal module is active
    Affected if The portal is enabled and accessible to users
  3. Check for contacts with profile pictures
    Review your iTop database or contacts module to determine if any contact records have uploaded profile pictures stored in the system
    Affected if Contacts with picture attachments exist in the iTop database
  4. Test the picture viewing endpoint
    If you have portal access, attempt to access a contact picture by modifying the ID parameter in the portal picture URL (for example, changing the contact ID in the picture request URL) to see if you can view pictures belonging to other contacts
    Affected if You can view pictures of contacts other than your own without proper authorization

Your environment is affected if iTop version is below 3.2.1 AND the portal is accessible AND your system contains contacts with profile pictures that could be accessed by unauthorized users.

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 3.2.1 or later
Fixed in 3.2.1
Interim mitigation

Upgrade iTop to version 3.2.1 or later, which contains the patch to enforce proper authorization before serving contact pictures.

Recommended fix Moderate confidence

3.2.1

  1. Create a full backup of the iTop installation directory and database
  2. Download iTop version 3.2.1 from the official iTop distribution (official github.com/combodo/itop repository or authorized distribution channel)
  3. Replace the existing iTop files with the files from version 3.2.1
  4. Run the iTop setup/upgrade script by accessing the iTop URL in a browser
  5. Follow the on-screen prompts to complete the database upgrade if required
  6. Log in as an administrator and verify the upgrade was successful
  7. Test that a portal user can no longer access other contacts' pictures by attempting to manipulate picture IDs in the URL
Caveat Review the iTop 3.2.1 release notes for any breaking changes or required migration steps before upgrading production instances

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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