Unauthenticated file disclosure via predictable charge numbers
Published Jan 8, 2026 · Updated Jan 8, 2026
Authorization bypass in OPEXUS eCASE eComplaint before 9.0.45.0 allows remote attackers to download files by guessing identifiers. The DocumentOpen.aspx endpoint accepts a predictable chargeNumber value and returns the associated document without enforcing object-level authorization. No authentication or user interaction is required, and enumeration exposes documents from other complaint cases while leaving integrity and availability unaffected.
Summary
What happened
Authorization bypass in OPEXUS eCASE eComplaint before 9.0.45.0 allows remote attackers to download files by guessing identifiers. The DocumentOpen.aspx endpoint accepts a predictable chargeNumber value and returns the associated document without enforcing object-level authorization. No authentication or user interaction is required, and enumeration exposes documents from other complaint cases while leaving integrity and availability unaffected.
The record
- CVE
- CVE-2026-22235
- Published
- Jan 8, 2026
- Updated
- Jan 8, 2026
- Vendor
- OPEXUS
- Product
- eCASE eComplaint
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2026CVE publishedPublication date reported by the CVE source.
- Jan 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <9.0.45.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo