Stored XSS via split name-field payload
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 run script in a victim's session. The account-profile screen fails to sanitize first- and last-name values separately, so payload fragments join and execute when the full name is rendered. An attacker needs an account and a victim must view the rendered name; the script then acts with the victim's browser-session access.
Summary
What happened
Stored XSS in OPEXUS eComplaint and eCASE before 10.2.0.0 allows remote authenticated users to run script in a victim's session. The account-profile screen fails to sanitize first- and last-name values separately, so payload fragments join and execute when the full name is rendered. An attacker needs an account and a victim must view the rendered name; the script then acts with the victim's browser-session access.
The record
- CVE
- CVE-2026-32868
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OPEXUS
- Product
- eCASE eComplaint
- Classifications
- CWE-79, T1189
- 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