Skip to main content
VulnerabilityPublished

CVE-2026-22232: OPEXUS eCASE Audit · Cross-site Scripting

Affects OPEXUS eCASE AuditSource CVE Database V5

0

Not known to be exploited · CVSS 4.8 Medium : upgrade to 11.14.2.0 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.14.2.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade OPEXUS eCASE Audit to 11.14.2.0.

Affected software

ProductAffectedFixed in
OPEXUSeCASE AuditAffected
  • >=11.4.0 <11.14.2.0
Fixed in
  • 11.14.2.0

AI-suggested

  1. Immediately upgrade OPEXUS eCASE Audit to version 11.14.2.0 or later where the vulnerability is patched.
  2. Implement strict input validation and output encoding on all user-supplied data fields, especially those rendered in HTML contexts.
  3. Restrict the ability to modify the 'A or SIC Number' field to trusted users only, minimizing the attack surface.
  4. Employ Content Security Policy (CSP) headers to limit the execution of unauthorized scripts within the application.
  5. Monitor application logs and user activity for unusual behavior indicative of attempted XSS exploitation.
  6. Conduct regular security training for users to recognize phishing or social engineering attempts that could lead to account compromise.
  7. Use multi-factor authentication (MFA) to reduce the risk of unauthorized access by attackers.
  8. Perform periodic security assessments and code reviews focusing on input handling and output encoding.
  9. Consider implementing web application firewalls (WAF) with rules to detect and block XSS payloads targeting this application.

Description

OPEXUS 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.

References

Community reviews

Loading reviews…