Stored XSS via unsanitized organization name
Published Mar 19, 2026 · Updated Mar 19, 2026
Stored XSS in OPEXUS eComplaint and eCASE before 10.2.0.0 allows remote authenticated users to execute script in a victim's session. The case-information workflow stores the Name of Organization value without correctly neutralizing it before rendering the case information page. Exploitation requires authenticated case-data entry and a victim to view the affected page, exposing data and actions available to that victim's application session.
Summary
What happened
Stored XSS in OPEXUS eComplaint and eCASE before 10.2.0.0 allows remote authenticated users to execute script in a victim's session. The case-information workflow stores the Name of Organization value without correctly neutralizing it before rendering the case information page. Exploitation requires authenticated case-data entry and a victim to view the affected page, exposing data and actions available to that victim's application session.
The record
- CVE
- CVE-2026-32869
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OPEXUS
- Product
- eCASE eComplaint
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <10.2.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo