Authenticated authorization bypass via client-side control tampering
Published Jan 8, 2026 · Updated Jan 8, 2026
Incorrect authorization in OPEXUS eCASE Audit 11.4.0 and later, before 11.14.1.0, allows remote authenticated users to access blocked functions. The web interface relies on disabled or administrator-blocked client-side controls, so modified JavaScript or crafted HTTP requests reach functions without corresponding server-side authorization enforcement. A valid account is required; exploitation exposes functions withheld by an administrator and can disclose data, alter data, or interrupt application service.
Summary
What happened
Incorrect authorization in OPEXUS eCASE Audit 11.4.0 and later, before 11.14.1.0, allows remote authenticated users to access blocked functions. The web interface relies on disabled or administrator-blocked client-side controls, so modified JavaScript or crafted HTTP requests reach functions without corresponding server-side authorization enforcement. A valid account is required; exploitation exposes functions withheld by an administrator and can disclose data, alter data, or interrupt application service.
The record
- CVE
- CVE-2026-22230
- Published
- Jan 8, 2026
- Updated
- Jan 8, 2026
- Vendor
- OPEXUS
- Product
- eCASE Audit
- Classifications
- CWE-863
- Attack vector
- network
- Privileges
- authenticated
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=11.4.0 <11.14.1.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