CVE-2026-32867
Access Control in Opexustech Ecase Ecomplaint ≤ 10.1.0.0
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/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:XSummary
CVE-2026-32867 is a medium-severity Forced Browsing (CWE-425) vulnerability in Opexustech Ecase Ecomplaint. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-32867 is a vulnerability in OPEXUS eComplaint versions prior to 10.1.0.0 that enables an unauthenticated attacker to obtain or guess an existing case number and upload arbitrary files via the 'Portal/EEOC/DocumentUploadPub.aspx' endpoint. Affected users would then see these unexpected files within cases, and an attacker could upload a large number of files to consume storage resources. The issue is rated at a CVSS v3.1 base score of 5.4 (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L) and is associated with CWE-425 (Direct Request ('Forced Browsing')) and CWE-639 (Authorization Bypass Through User-Controlled Key).
An unauthenticated remote attacker can exploit this vulnerability over the network with low attack complexity, though it requires user interaction. Exploitation allows the attacker to inject arbitrary files into existing cases by guessing or obtaining case numbers, leading to limited integrity impacts as legitimate users encounter unauthorized content. Additionally, mass file uploads can cause limited availability impacts through storage exhaustion.
Advisories recommend upgrading to OPEXUS eComplaint version 10.1.0.0 or later to mitigate the vulnerability. Key references include the CISA CSAF advisory at https://raw.githubusercontent.com/cisagov/CSAF/develop/csaf_files/IT/white/2025/va-26-077-01.json and the official CVE record at https://www.cve.org/CVERecord?id=CVE-2026-32867.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-13126
Vulnerability Data
OPEXUS eComplaint before version 10.1.0.0 allows an unauthenticated attacker to obtain or guess an existing case number and upload arbitrary files via 'Portal/EEOC/DocumentUploadPub.aspx'. Users would see these unexpected files in cases. Uploading a large number of files could consume storage.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.
AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.
AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.
Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.
Access control policy directly requires authorization checks on all resources, preventing forced browsing.
Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.
Privileged access rights control enforces least-privilege checks on restricted endpoints.
Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.