/

CVE-2026-31936

Severity:

HIGH RISK

(8.8)

Missing Authorization (CWE-862) in Combodo iTop Search

CVE-2026-31936

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Information Disclosure

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authorization vulnerability in Combodo iTop allows users to obtain information about objects they are not permitted to access through the search operation.

The issue becomes risky when search results or related object details are returned without consistently enforcing the requesting user's permissions.

Affected context

This issue affects iTop deployments where the search operation can process requests from authenticated users but does not reliably apply object-level authorization checks. The risk is greatest when searchable objects contain sensitive service, asset, customer, or operational information and access controls are enforced inconsistently between normal views and search results.

Exploit preconditions

  • Attack surface: The web application's search functionality
  • Required access: Access to an iTop account or interface that can invoke searches
  • Trigger point: A search operation involving objects outside the user's authorized scope
  • Why exploitation is possible: The search path may return object information without performing the same authorization checks applied to direct object access

Why this happens

The underlying bug is a missing authorization check in an object search workflow. The application appears to identify or return matching objects based on search criteria without consistently verifying whether the requesting user is allowed to view each result.

This maps to CWE-862: Missing Authorization, in which access to a protected resource is not adequately enforced after a user has been authenticated.

Potential impact

  • Unauthorized users may learn the existence of restricted objects
  • Sensitive object attributes or metadata could be disclosed
  • Information about customers, assets, incidents, or services may be exposed
  • Attackers could use returned information to support further targeted activity

General mitigation guidance

Mitigation typically focuses on enforcing authorization at every object retrieval and search-result construction boundary.

Common defensive patterns include:

  • Applying server-side, object-level authorization filters before returning search results
  • Reusing a centralized authorization policy for direct views, searches, exports, and APIs
  • Avoiding reliance on client-side filtering or hidden interface elements
  • Returning only fields and objects permitted by the requesting user's effective role and scope
  • Using least-privilege roles and narrowly defined object access policies
  • Treating search criteria and result identifiers as untrusted input

How teams detect issues like this

Organizations commonly detect missing authorization through:

  • Static analysis and code review of search handlers, query builders, and object serializers
  • Tests that compare search visibility with direct object-access permissions
  • Negative authorization tests using users with restricted scopes
  • Monitoring for searches that repeatedly reference objects outside a user's normal access pattern
  • Policy enforcement requiring server-side authorization checks for every data retrieval path

Automated application-security testing can help identify discrepancies between authenticated access and authorized object visibility.

Sources

SourceLink
github.comgithub.com/Combodo/iTop/commit/b3223eb9b6bc1514276f8f321db1e27db6f42808
github.comgithub.com/Combodo/iTop/security/advisories/GHSA-3r3r-j29m-3v43

Frequently asked

questions

It can be exploitable through the web application's search functionality when an attacker can submit searches to an affected iTop deployment.

Typically, the attacker needs at least the ability to access the search operation. Whether unauthenticated users are affected depends on the deployment's authentication and search-access configuration.

Enforce server-side, object-level authorization before including any object or field in search results, using the same policy applied to direct object access.

Maintain centralized authorization logic, apply deny-by-default permissions, and include negative tests that verify users cannot discover or retrieve objects outside their assigned scope.

Find out what's already
exploitable in your codebase.