CVE-2026-32868
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOPEXUS eComplaint and eCASE before 10.2.0.0 do not correctly sanitize the contents of first and last name fields in the 'My Information' screen. An authenticated attacker can inject parts of an XSS payload in the first and last name fields. The payload is executed when the full name is rendered. The attacker can run script in the context of a victim's session.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOPEXUS eComplaint and eCASE before version 10.2.0.0 contains a stored cross-site scripting (XSS) vulnerability in the 'My Information' screen where first and last name fields are not properly sanitized. An authenticated attacker can inject malicious JavaScript into these name fields, which executes when the full name is rendered elsewhere in the application, allowing session hijacking.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed eCASE or eComplaint versionLocate the application version number in the product interface, typically found in the Help > About section, system administration panel, or the login page footer. Compare this version number to the affected range: any version before 10.2.0.0.Affected if The installed version is a release earlier than 10.2.0.0 (e.g., 10.1.x, 10.0.x, 9.x).
-
Verify access to the My Information screenLog in as a standard authenticated user and navigate to the 'My Information' or 'My Profile' section of the eCASE or eComplaint application. Confirm this screen is accessible and displays editable name fields.Affected if The My Information screen is accessible and contains editable first name and last name input fields.
-
Test for XSS in name fieldsIn the My Information screen, enter a test payload such as <script>alert(1)</script> into the First Name and/or Last Name fields, save the changes, then navigate to other areas of the application where your full name is displayed (e.g., case assignments, reports, notifications).Affected if The payload executes as JavaScript (triggers an alert) when the name is rendered elsewhere in the application, indicating lack of output encoding.
-
Inspect application logs for XSS attemptsReview application security logs or audit logs for any entries indicating malicious input patterns in name fields, or check if the application has detected and sanitized prior XSS attempts.Affected if No sanitization is logged and no protective filters are triggered when special characters are submitted in name fields.
A user is affected if the installed eCASE or eComplaint version is earlier than 10.2.0.0 AND the My Information screen is accessible for editing name fields, with the injected content executing as script when displayed in other parts of the application.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.2.0.0
Upgrade to version 10.2.0.0 or later which includes proper input sanitization for name fields; additionally, implement output encoding when rendering user-supplied name data throughout the application.
10.2.0.0 or later
- Confirm current Ecase eComplaint/eCASE version by checking the application admin panel or system information
- Review release notes for version 10.2.0.0 to understand changes and any prerequisites
- Create a backup of the current database and configuration files
- Schedule a maintenance window for the upgrade process
- Download version 10.2.0.0 or later from the official OPEXUS distribution channel
- Follow the vendor's standard upgrade procedure for Ecase eComplaint/eCASE
- After upgrade, verify that the 'My Information' screen now properly sanitizes first and last name fields
- Test that saved names render safely without executing injected scripts
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32868 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32868 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data