LiveActive security incident?Get immediate response
CVE Record

CVE-2026-22230: OPEXUS eCASE Audit incorrect access control

OPEXUS eCASE Audit allows an authenticated attacker to modify client-side JavaScript or craft HTTP requests to access functions or buttons that have been disabled or blocked by an administrator. Fixed in eCASE Platform 11.14.1.0.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-22230 is an authorization flaw in OPEXUS eCASE Audit. A logged-in user may reach functions that administrators intended to disable or block. This can expose sensitive data and allow limited unauthorized changes. The vendor states it is fixed in eCASE Platform 11.14.1.0.

Executive priority

Prioritize remediation for environments containing sensitive case, audit, or compliance data. This is not cited as actively exploited, but authenticated users could bypass administrative restrictions. Treat as a high-priority application update and access-control review.

Technical view

The issue is CWE-863 incorrect authorization. An authenticated attacker can alter client-side JavaScript or craft HTTP requests to invoke disabled or blocked functions/buttons. CVSS 3.1 is 7.6 high: network accessible, low complexity, low privileges, no user interaction, with high confidentiality impact and low integrity/availability impact.

Likely exposure

Organizations running OPEXUS eCASE Audit are potentially exposed, especially where many internal or external authenticated users access the platform. The provided data names eCASE Audit and references a fix in eCASE Platform 11.14.1.0, but affected-version details should be confirmed against vendor guidance.

Exploitation context

No CISA KEV listing or provided source indicates active exploitation. Exploitation requires authenticated access, reducing drive-by risk, but the flaw can bypass administrative UI restrictions and may matter in multi-user case management environments handling sensitive records.

Researcher notes

The public description points to missing server-side authorization enforcement for functions hidden or blocked in the client UI. Avoid assuming client-side controls are security boundaries. The source bundle does not provide exploit indicators, detailed affected ranges, or compensating controls beyond the stated fixed release.

Mitigation direction

  • Upgrade to eCASE Platform 11.14.1.0 if vendor guidance confirms applicability.
  • Review OPEXUS release notes and advisories for affected-version clarification.
  • Restrict eCASE Audit access to trusted users until remediated.
  • Monitor for unusual access to disabled or restricted functions.

Validation and detection

  • Inventory OPEXUS eCASE Audit and eCASE Platform versions.
  • Confirm whether deployed versions are covered by OPEXUS guidance.
  • Verify upgrade status against 11.14.1.0 release notes.
  • Review application logs for unexpected use of restricted features.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22230 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L2.84.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2026-22230Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

  • CVE List V5 sourceCVE List V5
  • urlCVE reference · release-notes
  • urlCVE reference · vdb-entry
  • urlCVE reference · government-resource, third-party-advisory
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OPEXUSeCASE Audit11.4.0, 11.14.1.0unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.