PatchTheCVEecase ecomplaint vulnerabilities and fixes
Recent CVEs affecting ecase ecomplaint, with upgrade or downgrade steps. 6 tracked.
Also searched as: ecaseecomplaint.
ecase ecomplaint has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 6. Most recent: 2026-03-19. Highest priority: CVE-2026-32865 (score 45/100).
- CVE-2026-32869 MEDIUM 5.5 UPGRADE OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of the "Name of Organizatio
- CVE-2026-32868 MEDIUM 5.5 UPGRADE OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fiel
- CVE-2026-32867 MEDIUM 5.4 UPGRADE OPEXUS eComplaint before version 10.1.0.0 allows an unauthenticated attacker to obtain or guess an existing ca
- CVE-2026-32866 MEDIUM 5.5 UPGRADE OPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fiel
- CVE-2026-32865 CRITICAL 9.8 UPGRADE OPEXUS eComplaint and eCASE before version 10.1.0.0 include the secret verification code in the HTTP response
- CVE-2026-22235 HIGH 7.5 UPGRADE OPEXUS eComplaint before version 9.0.45.0 allows an attacker to visit the the 'DocumentOpen.aspx' endpoint, it
FAQ
How do I fix ecase ecomplaint vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is ecase ecomplaint being exploited right now?
None of the tracked ecase ecomplaint CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which ecase ecomplaint CVE should I patch first?
CVE-2026-32865 currently ranks highest (45/100): OPEXUS eComplaint and eCASE before version 10.1.0.0 include the secret verification code in the HTTP response .