CVE-2026-22232
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 eCASE Audit allows an authenticated attacker to save JavaScript in the "A or SIC Number" field within the Project Setup functionality. The JavaScript is executed whenever another user views the project. Fixed in OPEXUS eCASE Audit 11.14.2.0.
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 eCASE Audit contains a stored XSS vulnerability in the Project Setup functionality. An authenticated attacker can inject malicious JavaScript into the 'A or SIC Number' field, which executes in the browsers of other users when they view the affected project.
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>= 11.4.0, < 11.14.2.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 Audit versionAccess the application admin panel or system information page, typically found under Help > About or System Administration > Version Info. Compare the displayed version number against the affected range of >= 11.4.0 and < 11.14.2.0.Affected if Version is 11.4.0 through 11.14.1.x (any build below 11.14.2.0)
-
Verify Project Setup module is accessibleLog in as a standard user or admin and navigate to the Project Setup or Projects section. Confirm the 'A or SIC Number' field is present and editable in the project creation or editing interface.Affected if The Project Setup functionality with the 'A or SIC Number' field is available and enabled in the application
-
Inspect application logs for XSS patterns in SIC fieldSearch application logs (typically in /logs or via the admin logging console) for entries containing script tags, javascript:, or HTML event handlers (onclick, onerror, etc.) within what appears to be SIC number or project setup data.Affected if Log entries contain malicious script payloads or encoded XSS patterns in project/SIC-related fields
-
Review database for stored XSS payloadsQuery the project or case database tables (commonly named Projects, Cases, or similar) for the 'A or SIC Number' field. Look for non-numeric characters, HTML tags, or JavaScript code stored in this field.Affected if The database contains HTML tags, script elements, or JavaScript code in the SIC Number field
Your environment is affected if eCASE Audit version is between 11.4.0 and 11.14.1.x AND the Project Setup module with the 'A or SIC Number' field is in use.
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 · scoped11.14.2.0
Upgrade to OPEXUS eCASE Audit version 11.14.2.0 or later, which includes proper input sanitization for the affected field.
11.14.2.0
- Backup the current OPEXUS eCASE Audit installation and database
- Download OPEXUS eCASE Audit version 11.14.2.0 from the official vendor source
- Apply the upgrade following OPEXUS vendor documentation for version 11.14.2.0
- Verify the upgrade was successful by logging in and checking the version
- Confirm the "A or SIC Number" field in Project Setup no longer executes stored JavaScript
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22232 — 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-22232 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