OPEXUS eComplaint IDOR

published 2026-01-08 10 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-1485

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits: 0; none known

OPEXUS eComplaint before version 9.0.45.0 allows an attacker to visit the the 'DocumentOpen.aspx' endpoint, iterate through predictable values of 'chargeNumber', and download any uploaded files.

Patch / fix

fixed in 1

OPEXUS eComplaint 9.0.45.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa vex VA-26-008-02 updated 2026-01-07 cvss 7.5

OPEXUS eComplaint and eCasePortal IDOR

OPEXUS eComplaint <9.0.45.0
affected: vendor fix
OPEXUS eComplaint 9.0.45.0
fixed: vendor fix

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 10 mo ago (2026-01-08)

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA	4.0	8.7	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
CNA	4.0	8.7	CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

OPEXUS eComplaint

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key

References

raw.githubusercontent.com /cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-008-02.json
government-resource, third-party-advisory, broken-link
cve.org /CVERecord?id=CVE-2026-22235
vdb-entry, third-party-advisory

Sources

CVE List CVE-2026-22235
NVD CVE-2026-22235

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary