/

CVE-2026-30866

Severity:

HIGH RISK

(7.5)

Information Disclosure (CWE-200) in iTop File Uploads

CVE-2026-30866

Deferred

Vulnerability type

Category:

Information Disclosure

CWE:

CWE-200, CWE-306

Impact:

Unauthorized access to sensitive uploaded files

Severity:

HIGH RISK

(7.5)

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

Combodo iTop may expose sensitive uploaded files through URLs that can be obtained or observed by an unauthorized party. When access controls are not applied to these file URLs, unauthenticated users may retrieve protected content.

Affected context

The issue occurs in iTop deployments where uploaded files are served through directly accessible URLs without sufficient authorization checks. Risk is higher when those URLs are exposed through logs, browser history, referrers, network observation, or other forms of URL disclosure.

Exploit preconditions

  • Attack surface: Web-accessible uploaded-file URLs
  • Required access: No authenticated account may be necessary if a valid file URL has been obtained
  • Trigger point: A request to an uploaded file using an exposed or observed URL
  • Why exploitation is possible: File retrieval may not verify that the requester is authorized to access the associated content

Why this happens

The underlying issue is insufficient access control around uploaded-file retrieval. A file URL is treated as sufficient authorization, allowing possession or observation of the URL to substitute for an authenticated permission check. This maps primarily to CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, with CWE-306: Missing Authentication for Critical Function also relevant where file access is available without authentication.

Potential impact

  • Unauthorized users may read sensitive uploaded documents
  • Confidential business, operational, or personal information could be disclosed
  • Exposed files may support further social engineering or targeted attacks
  • Organizations could face privacy, compliance, or reputational consequences

General mitigation guidance

Mitigation typically focuses on making authorization independent of possession of a file URL and reducing the exposure of uploaded content.

Common defensive patterns include:

  • Requiring authentication and object-level authorization for every file download
  • Using short-lived, scoped access tokens for intentionally shareable files
  • Avoiding predictable or permanently valid file URLs
  • Storing uploaded content outside directly public web paths
  • Applying least-privilege access to file storage and application service accounts
  • Limiting sensitive data retention and removing unnecessary uploaded content
  • Preventing sensitive URLs from appearing in logs, referrers, and client-visible metadata where practical

How teams detect issues like this

Organizations commonly detect this class of issue through:

  • Static analysis and code review of file-download handlers for missing authorization checks
  • Dynamic tests that request uploaded-file URLs with no session or an unrelated account
  • Web and application log reviews for unauthenticated file access
  • Policy checks requiring object-level authorization before serving stored content
  • Automated security testing that verifies URL possession alone does not grant access

Sources

SourceLink
github.comgithub.com/Combodo/iTop/commit/458a996c29db73b9ce2d374f6ce8b90c36351159
github.comgithub.com/Combodo/iTop/security/advisories/GHSA-8rgc-qjf3-xqq4

Frequently asked

questions

Yes. If an uploaded-file URL is exposed and the application serves it without adequate authorization, an attacker may access the file remotely without being on the host network.

Not necessarily. The described condition allows unauthenticated access when an attacker obtains or observes a valid file URL.

Require authentication and object-level authorization for each file request rather than treating possession of a URL as proof of permission.

Keep sensitive uploads out of public paths, use scoped and time-limited sharing mechanisms, test unauthenticated access paths, and enforce access-control checks in code review and security policies.

Find out what's already
exploitable in your codebase.