LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22235: OPEXUS eComplaint IDOR

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.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

OPEXUS eComplaint versions before 9.0.45.0 can expose uploaded files without authentication. An attacker could access a document endpoint and use predictable charge numbers to retrieve files belonging to other cases. The main business risk is unauthorized disclosure of sensitive complaint documents.

Executive priority

Treat this as a high-priority confidentiality issue. If eComplaint stores sensitive employee, customer, or case documents, exposure could create privacy, compliance, and reputational impact. Prioritize version validation, remediation, and document-access log review.

Technical view

CVE-2026-22235 is an insecure direct object reference in OPEXUS eComplaint. The DocumentOpen.aspx endpoint accepts predictable chargeNumber values, allowing unauthenticated network attackers to download uploaded files. The CVSS 4.0 score is 8.7, with high confidentiality impact and no integrity or availability impact cited.

Likely exposure

Organizations running OPEXUS eComplaint before 9.0.45.0 are potentially exposed, especially if the application is reachable from untrusted networks. The source data does not identify affected deployment models, authentication configurations, or whether internet exposure is common.

Exploitation context

The CVE describes low-complexity remote access with no privileges or user interaction required. CISA KEV status is false in the provided data, and no cited source states active exploitation. The described weakness is enumeration of predictable identifiers, not code execution.

Researcher notes

The public description maps to CWE-639 authorization bypass through user-controlled keys. Evidence is limited to the CVE and CSAF-style advisory references. No exploit code, patch notes, affected hosting details, or incident reports are included in the supplied sources.

Mitigation direction

  • Upgrade OPEXUS eComplaint to version 9.0.45.0 or later, if available from the vendor.
  • Restrict access to eComplaint from untrusted networks until remediation is complete.
  • Review vendor guidance for any additional configuration or compensating controls.
  • Assess whether exposed uploaded documents contained regulated or sensitive information.

Validation and detection

  • Inventory OPEXUS eComplaint instances and record their installed versions.
  • Confirm whether any instance is earlier than 9.0.45.0.
  • Review application access logs for unusual DocumentOpen.aspx access patterns.
  • Validate that document access controls prevent cross-case file retrieval after remediation.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22235 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: 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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-22235Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OPEXUSeComplaint0, 9.0.45.0unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.