Stored XSS via split profile name payload
Published Mar 19, 2026 · Updated Mar 19, 2026
Stored XSS in OPEXUS eCASE before 10.2.0.0 allows remote authenticated users to run scripts in a victim's session. The profile editor stores unsanitized fragments split across first- and last-name fields, then renders the combined full name as executable page content. An account and a victim who views the rendered name are required, exposing only data and actions available to the victim's browser session.
Summary
What happened
Stored XSS in OPEXUS eCASE before 10.2.0.0 allows remote authenticated users to run scripts in a victim's session. The profile editor stores unsanitized fragments split across first- and last-name fields, then renders the combined full name as executable page content. An account and a victim who views the rendered name are required, exposing only data and actions available to the victim's browser session.
The record
- CVE
- CVE-2026-32866
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- OPEXUS
- Product
- eCASE
- Classifications
- CWE-79, T1203
- 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.1.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