VulnerabilityPublished 19 Mar 2026

CVE-2026-32867: OPEXUS eComplaint · Insecure Direct Object Reference

Affects OPEXUS eComplaintSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
OPEXUSeComplaint	Affected <10.1.0.0	Fixed in–

AI-suggested

Organizations should upgrade OPEXUS eComplaint to version 10.1.0.0 or later where this vulnerability is addressed. In the absence of an immediate patch, implement strict access controls to restrict access to the 'DocumentUploadPub.aspx' endpoint, such as IP whitelisting or VPN-only access. Employ input validation and verify case numbers server-side to prevent unauthorized file uploads. Monitor file upload activity for anomalies, including unusual volume or unexpected file types. Implement storage quotas and automated cleanup policies to mitigate storage exhaustion risks. Conduct regular audits of uploaded files to detect unauthorized content. Additionally, consider deploying web application firewalls (WAFs) with custom rules to block unauthorized upload attempts. Educate users to report unexpected files appearing in cases promptly. Finally, maintain up-to-date backups to recover from potential data integrity issues caused by exploitation.

Description

CVE-2026-32867 is a medium severity vulnerability in OPEXUS eComplaint versions prior to 10.1.0.0 that allows unauthenticated attackers to upload arbitrary files by guessing existing case numbers via the 'Portal/EEOC/DocumentUploadPub.aspx' endpoint. This authorization bypass through user-controlled keys (CWE-639) enables attackers to inject unexpected files into complaint cases, potentially causing data integrity issues and storage exhaustion. Exploitation requires no authentication but does require user interaction, such as triggering file uploads. While no known exploits are currently reported in the wild, the vulnerability could be leveraged to disrupt case management or facilitate further attacks. Organizations using OPEXUS eComplaint should prioritize patching and implement strict access controls and input validation to mitigate risks. Countries with significant deployments of OPEXUS eComplaint, particularly those with regulatory complaint management needs, are at higher risk.

Impact

The vulnerability allows attackers to inject arbitrary files into complaint cases, undermining the integrity of case data and potentially misleading users or administrators. This can disrupt complaint processing workflows and damage organizational trust in the system. The ability to upload many files can exhaust storage resources, causing denial-of-service conditions that degrade availability of the eComplaint platform. Although confidentiality is not directly impacted, the integrity and availability issues can have significant operational consequences, especially for organizations relying on eComplaint for regulatory or legal case management. Attackers could also use this vector as a foothold for further attacks, such as uploading malicious files or triggering application errors. The impact is particularly critical for organizations handling sensitive or high-volume complaint data, where data integrity and system uptime are paramount.

Summary

CVE-2026-32867 identifies a security flaw in OPEXUS eComplaint software versions before 10.1.0.0, where an unauthenticated attacker can bypass authorization controls by exploiting a user-controlled key mechanism related to case numbers. Specifically, the vulnerability resides in the 'Portal/EEOC/DocumentUploadPub.aspx' endpoint, which allows attackers to upload arbitrary files to complaint cases by guessing or obtaining valid case numbers. This is categorized under CWE-639 (Authorization Bypass Through User-Controlled Key) and CWE-425 (Direct Request). The attacker does not need valid credentials but must interact with the system to upload files. Uploaded files appear in the targeted cases, potentially confusing users and corrupting case data integrity. Additionally, uploading a large volume of files can lead to storage exhaustion, impacting system availability. The vulnerability does not disclose sensitive information directly but compromises data integrity and availability. No patches or exploits are currently documented, but the risk remains due to the ease of exploitation (no authentication required) and the potential for denial-of-service through resource consumption. The CVSS 3.1 base score is 5.4, reflecting network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and low availability impact.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-425Direct Request (Forced Browsing) (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
Architecture and Design · Operation
Apply appropriate access control authorizations for each access to all restricted URLs, scripts or files.
Architecture and Design
Consider using MVC based frameworks such as Struts.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
Attack patterns
Directory Indexing (opens in a new tab)
Detect Unpublicized Web Pages (opens in a new tab)
Detect Unpublicized Web Services (opens in a new tab)
Key Negotiation of Bluetooth Attack (KNOB) (opens in a new tab)
Forceful Browsing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 19:28 UTC

WeaknessesCWE-639, CWE-425

Technical details

References

Community reviews

Related threats