/

CVE-2026-22235

Severity:

HIGH RISK

(7.5)

Insecure Direct Object Reference in OPEXUS eComplaint

CVE-2026-22235

Analyzed

Vulnerability type

Category:

Insecure Direct Object Reference

CWE:

CWE-639

Impact:

Unauthorized File Disclosure

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

OPEXUS eComplaint before version 9.0.45.0 exposes a document download endpoint that allows attackers to iterate through predictable chargeNumber values and access arbitrary uploaded files.

When the application fails to properly enforce authorization on document access, an attacker can systematically guess identifiers and retrieve documents they are not entitled to view.

Affected context

This vulnerability occurs in OPEXUS eComplaint instances that expose the DocumentOpen.aspx endpoint to users who can supply or manipulate the chargeNumber parameter.

The issue arises where document identifiers are predictable or sequential and where access control checks are tied only to the presence of a valid identifier, rather than to the requesting user's permissions for the associated case or record.

Environments that allow broad or unvalidated access to this endpoint are more likely to be affected.

Exploit preconditions

  • Attack surface: HTTP access to the DocumentOpen.aspx endpoint in the eComplaint application.
  • Required access: Network or web access to the application; no specific authorization to each target document if the endpoint is exposed after a low-bar login or, in some deployments, possibly without authentication.
  • Trigger point: Supplying or modifying the chargeNumber parameter and issuing repeated requests with guessed or iterated values.
  • Why exploitation is possible: The server uses the supplied chargeNumber as a direct reference to backend files without consistently verifying that the requester is authorized to access the underlying complaint or document.

Why this happens

The underlying bug corresponds to CWE-639: Authorization Bypass Through User-Controlled Key.

The application treats chargeNumber as a trusted, direct reference to stored documents and relies on its obscurity or validity alone, rather than checking whether the current user has rights to the associated complaint or file.

Because identifiers are predictable or enumerable and are not bound to the current user's access context, an attacker can systematically traverse the identifier space and retrieve documents that belong to other users or cases.

Potential impact

  • Unauthorized viewing of uploaded complaint documents that may contain sensitive or personal information.
  • Exposure of internal investigation materials, evidence, or confidential case attachments.
  • Privacy violations affecting complainants, staff, or third parties.
  • Regulatory or legal exposure due to mishandling of protected or regulated data.
  • Intelligence gathering that can facilitate further social engineering or targeted attacks.

General mitigation guidance

Effective mitigation typically centers on strong, object-level authorization checks and non-enumerable identifiers:

  • Enforce access control at the document level by verifying, on every request, that the current user is authorized for the complaint or case associated with the requested file.
  • Avoid relying solely on predictable numeric identifiers for sensitive resources; consider opaque, non-guessable identifiers that are mapped server-side.
  • Decouple client-controlled parameters from direct database keys by using internal lookups that always reference the current user's permitted scope.
  • Implement a consistent authorization layer or middleware for all file and record access endpoints, rather than handling checks ad hoc.
  • Apply the principle of least privilege so that users see only records and documents they strictly need.

How teams detect issues like this

Detection often involves a mix of code-centric analysis and runtime monitoring:

  • Static analysis and code review: Search for endpoints that retrieve documents or records based on request parameters (e.g., chargeNumber) without verifying user ownership, role, or case membership.
  • Pattern-based review: Flag direct use of request parameters as primary keys in data access calls, especially where there is no centralized authorization component invoked.
  • Automated tools: Use application security testing tools (e.g., SAST/DAST) configured to look for IDOR/authorization bypass patterns and test for parameter tampering.
  • Logging and analytics: Monitor access logs for unusual access patterns, such as sequential chargeNumber requests or users reading large numbers of unrelated files.

Sources

SourceLink
raw.githubusercontent.comraw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-008-02.json
cve.orgcve.org/CVERecord?id=CVE-2026-22235

Frequently asked

questions

Yes. Anyone with network access to the affected eComplaint instance and the DocumentOpen.aspx endpoint can attempt to exploit the issue, subject to whatever minimal access control is in place.

The attacker needs the same level of access required to reach the document download endpoint. In some deployments this may require basic authentication or an application account; in others, the endpoint may be reachable from any user with general access to the system.

Introduce robust, centralized authorization checks that validate, on each document download request, that the requesting user is allowed to access the case or record associated with the given identifier, and avoid using raw, user-supplied identifiers directly for file retrieval.

Design the application so that every access to a record or file passes through a consistent authorization layer, use non-guessable identifiers for sensitive objects, enforce the principle of least privilege, and incorporate authorization-focused tests and secure code review into the development lifecycle.

Find out what's already
exploitable in your codebase.