CVE-2026-32866
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 a user profile. An authenticated attacker can inject parts of an XSS payload in their first and last name fields. The payload is executed when the user's 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 confidenceThis is a stored Cross-Site Scripting (XSS) vulnerability in OPEXUS eComplaint and eCASE. Authenticated users can inject malicious JavaScript into first and last name profile fields. The payload executes when the user's full name is rendered anywhere in the application, allowing the attacker to steal session cookies or perform actions in the victim's context.
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 the installed version of OPEXUS eComplaint or eCASELocate the version information in the application admin panel, about page, or configuration files. Compare your installed version against the affected range: versions prior to 10.2.0.0 are vulnerable.Affected if The installed version is less than 10.2.0.0
-
Verify that user profile management is accessible to authenticated usersLog in as a standard authenticated user and navigate to the profile or user settings section where first name and last name fields can be edited.Affected if Authenticated users can access and modify their own profile name fields
-
Inspect existing user profile name fields for untrusted contentQuery the user profile database or inspect the first_name and last_name fields directly to see if any contain HTML or script tags such as <script>, javascript:, or event handlers like onload or onerror.Affected if Any user record contains raw HTML or script syntax in name fields that is not escaped
-
Test for reflected output of user names without encodingWith a low-privilege authenticated account, modify your first or last name to include a harmless test string such as <img src=x onerror=alert(1)> and then view any area of the application where your full name is displayed (e.g., dashboard, comments, logs).Affected if The test string renders as executable HTML rather than being displayed as plain text
-
Check application logs or security monitoring for XSS indicatorsReview application logs, intrusion detection alerts, or browser console warnings for patterns indicating XSS attempts or successful script injection via name fields.Affected if Logs show evidence of script injection attempts or successful XSS execution through user name fields
A user is affected if the installed version is below 10.2.0.0 and the application allows authenticated users to modify profile name fields that are subsequently rendered without output encoding.
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 implements proper sanitization of first and last name fields. As a temporary workaround, ensure all user-provided name data is output-encoded when rendered.
10.2.0.0
- Upgrade OPEXUS eComplaint/eCASE to version 10.2.0.0 or later
- After upgrading, verify the XSS vulnerability is patched by attempting to inject a benign script payload (e.g., <script>alert(1)</script>) in the first and last name fields of a test user profile
- Confirm the payload is rendered as text rather than executed when the user's full name is displayed elsewhere in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32866 — 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-32866 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