{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-32867 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-32867 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32867 is a medium-severity vulnerability in OPEXUS eComplaint, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-32867 and fix it if it is affected.\n\nWhat it is: CVE-2026-32867 is a medium-severity vulnerability in OPEXUS eComplaint, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-32867 in the wild and no public exploit code.\n\nAffected product: OPEXUS eComplaint. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32867/ (Markdown: https://insights.sbomify.com/CVE-2026-32867/index.md)","id":"CVE-2026-32867","markdown":"https://insights.sbomify.com/CVE-2026-32867/index.md","name":"CVE-2026-32867","record":{"aliases":["GHSA-qw9c-jpw9-vj74"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"eComplaint web application","requires_auth":"none","summary":"Unauthenticated attackers can upload arbitrary files to eComplaint cases by guessing case numbers, leading to data modification and potential storage exhaustion.","user_interaction":"required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[{"product":"ecase_ecomplaint","vendor":"opexustech"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"},{"id":"CWE-425","name":"Direct Request"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"OPEXUS eComplaint unauthenticated file upload","id":"CVE-2026-32867","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OPEXUS eComplaint and eCASE XSS via my information","id":"CVE-2026-32868"},"packages":[],"prev":{"headline":"OPEXUS eComplaint and eCase stored XSS via profile first and last name","id":"CVE-2026-32866"},"products":["eComplaint"],"published":"2026-03-19","related":[{"cvss_score":9.2,"headline":"OPEXUS eComplaint and eCase insecure password reset","id":"CVE-2026-32865","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":8.7,"headline":"OPEXUS eComplaint IDOR","id":"CVE-2026-22235","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":5.1,"headline":"OPEXUS eComplaint and eCase stored XSS via profile first and last name","id":"CVE-2026-32866","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":5.1,"headline":"OPEXUS eComplaint and eCASE XSS via my information","id":"CVE-2026-32868","kev_date_added":null,"published":"2026-03-19"},{"cvss_score":5.1,"headline":"OPEXUS eComplaint and eCASE XSS via Name of Organization field","id":"CVE-2026-32869","kev_date_added":null,"published":"2026-03-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-19","vendors":["OPEXUS"]},"summary":"Unauthenticated attackers can upload arbitrary files to eComplaint cases by guessing case numbers, leading to data modification and potential storage exhaustion.","url":"https://insights.sbomify.com/CVE-2026-32867/"}