CVE-2026-32867
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 · uneditedOPEXUS 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.
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 confidenceOPEXUS eComplaint before version 10.1.0.0 contains an insecure direct object reference (IDOR) vulnerability combined with unrestricted file upload. An unauthenticated attacker can obtain or guess valid case numbers and upload arbitrary files through the DocumentUploadPub.aspx endpoint, causing unexpected files to appear in cases and potentially consuming storage with large uploads.
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< 10.1.0.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed eComplaint versionLocate the version number in the application (typically found in the application's About page, header footer, or configuration files such as web.config or version.info in the application root directory). Compare this version to the affected range: any version below 10.1.0.0 is vulnerable.Affected if The installed version is any release prior to 10.1.0.0
-
Verify DocumentUploadPub.aspx endpoint existsCheck the application's web directory for the presence of DocumentUploadPub.aspx. This file is typically located in the web application's root or a public forms subdirectory. If the file exists and the version is below 10.1.0.0, the vulnerability is present.Affected if The DocumentUploadPub.aspx file exists in the deployed application and the version is below 10.1.0.0
-
Confirm endpoint is network-accessibleDetermine whether the DocumentUploadPub.aspx endpoint is reachable from unauthenticated network paths (external network, DMZ, or without requiring login). Check network firewall rules, web server authentication requirements, and application-level access controls.Affected if The endpoint does not require authentication and is reachable from untrusted networks or anonymous users
Your environment is affected if you are running OPEXUS eComplaint version lower than 10.1.0.0 and the DocumentUploadPub.aspx endpoint is present and accessible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.1.0.0
Upgrade to OPEXUS eComplaint version 10.1.0.0 or later to remediate this vulnerability.
10.1.0.0
- Obtain the official OPEXUS eComplaint version 10.1.0.0 or later from OPEXUS official channels
- Deploy the upgrade in a non-production environment first to validate functionality
- Apply the upgrade to production environments following standard OPEXUS upgrade procedures
- After upgrading, verify that the Portal/EEOC/DocumentUploadPub.aspx endpoint no longer accepts unauthenticated uploads
- Audit existing cases for any unexpected files that may have been uploaded during any prior exploitation
- Review and enforce proper authentication and authorization controls on all document upload endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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