dbcve.org
Ecase EcomplaintApplication · Opexustech

CVE-2026-22235

HIGH · 7.5 CVSS v3.1 Published 2026-01-08
Fix available
A fix is available. Upgrade to 9.0.45.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OPEXUS eComplaint before version 9.0.45.0 contains an Insecure Direct Object Reference (IDOR) vulnerability in the DocumentOpen.aspx endpoint. The chargeNumber parameter uses predictable sequential values, allowing unauthenticated attackers to enumerate and download any uploaded files by manipulating this parameter.

MitigationUpgrade to eComplaint version 9.0.45.0 or later which addresses this vulnerability. Alternatively, implement proper authorization checks on the DocumentOpen.aspx endpoint to verify user permissions before serving files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ecase EcomplaintApplication
Affected:< 9.0.45.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify eComplaint installation and version
    Locate the eComplaint installation directory and check the version information file, or query the application metadata (often found in assembly info, version.config, or the application's about page). Compare the installed version number to the affected range: versions before 9.0.45.0 are vulnerable.
    Affected if The installed version is lower than 9.0.45.0
  2. Verify DocumentOpen.aspx endpoint exists
    Check if the file DocumentOpen.aspx exists within the web application's directories (typically in the root or a documents handling module). This can be done by inspecting the web application file structure on the server or checking HTTP response when accessing the endpoint directly.
    Affected if The DocumentOpen.aspx file exists in the application deployment
  3. Confirm endpoint permits unauthenticated access
    Attempt to access the DocumentOpen.aspx endpoint without providing credentials (no login session). Send a GET request to DocumentOpen.aspx and verify if the server returns the page content or a generic response rather than redirecting to a login page or returning a 401/403 error.
    Affected if The endpoint is accessible without authentication (no login required)
  4. Test parameter predictability for IDOR
    Submit requests to DocumentOpen.aspx with different chargeNumber parameter values (e.g., 1, 2, 3, or other sequential numbers). Observe if the application accepts these values and returns different documents without performing authorization checks.
    Affected if Different chargeNumber values return documents without authorization validation

A user is affected if eComplaint version is below 9.0.45.0 AND the DocumentOpen.aspx endpoint exists and accepts unauthenticated requests with predictable chargeNumber parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.0.45.0 or later
Fixed in 9.0.45.0
Interim mitigation

Upgrade to eComplaint version 9.0.45.0 or later which addresses this vulnerability. Alternatively, implement proper authorization checks on the DocumentOpen.aspx endpoint to verify user permissions before serving files.

Recommended fix High confidence

9.0.45.0

  1. Identify the current installed version of OPEXUS eComplaint
  2. Contact OPEXUS vendor or consult official release notes to obtain version 9.0.45.0 or later
  3. Plan and schedule the upgrade in a non-production environment first
  4. Test the upgrade to verify the IDOR vulnerability is remediated and the application functions correctly
  5. Deploy the upgrade to production environment
  6. Verify that the DocumentOpen.aspx endpoint now properly enforces authorization checks

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ecase Ecomplaint Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22235 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data