dbcve.org
Tririga Application PlatformApplication · Ibm

CVE-2026-11372

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
IBM TRIRIGA Application Platform 5.0.2 through 5.0.3 is vulnerable to cross-site scripting. This vulnerability allows an authenticated user to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted 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 confidence

IBM TRIRIGA Application Platform versions 5.0.2 through 5.0.3 contains a stored cross-site scripting (XSS) vulnerability. An authenticated user can embed arbitrary JavaScript code into the Web UI, which executes in the browsers of other users viewing the affected interface, potentially exposing credentials or session data within a trusted session.

MitigationApply the IBM-provided patch or upgrade to a version beyond 5.0.3. Implement output encoding and input validation as compensating controls until the vendor fix is available. Review and enforce Content Security Policy headers.

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
Tririga Application PlatformApplication
Affected:= 5.0.2= 5.0.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify IBM TRIRIGA version
    Access the IBM TRIRIGA administration console or check the installed version through the system's 'About' or version information page. Common paths include the admin dashboard or system information panel within the application.
    Affected if The installed version is exactly 5.0.2 or 5.0.3
  2. Confirm Web UI is enabled
    Check if the IBM TRIRIGA web interface is accessible and active. Verify that users can log in through the browser-based UI.
    Affected if The Web UI is accessible and users can authenticate to the platform
  3. Review application audit logs for XSS payloads
    Examine IBM TRIRIGA audit logs or database records for any suspicious JavaScript tags, script elements, or event handler attributes (such as onerror, onload) that may have been submitted through form fields or interface inputs.
    Affected if Logs or stored data contain unsanitized script tags or JavaScript event handlers
  4. Inspect user-submitted content storage
    Check database tables or content management areas where user input is stored and rendered in the Web UI, such as document metadata, user profiles, or custom fields.
    Affected if Stored content allows rendering of raw HTML or script tags without output encoding
  5. Verify Content Security Policy configuration
    Check the web server or application configuration for Content-Security-Policy headers. Inspect if the CSP allows inline scripts (unsafe-inline) or sources not explicitly whitelisted.
    Affected if CSP is missing, not enforced, or permits inline script execution

A user is affected if they are running IBM TRIRIGA Application Platform version 5.0.2 or 5.0.3 with the Web UI enabled and authentication available to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the IBM-provided patch or upgrade to a version beyond 5.0.3. Implement output encoding and input validation as compensating controls until the vendor fix is available. Review and enforce Content Security Policy headers.

Recommended fix Moderate confidence

Upgrade to a stable release newer than 5.0.3 (e.g., 5.1.0 or latest available stable version)

  1. 1. Identify the current IBM TRIRIGA Application Platform version in use (should be 5.0.2 or 5.0.3 as stated in the CVE).
  2. 2. Check IBM's official support portal or security bulletins for the specific patch addressing CVE-2026-11372.
  3. 3. If a patch is available, apply it following IBM's standard patch deployment procedures for TRIRIGA.
  4. 4. If no specific patch is available, upgrade to a version newer than 5.0.3 (e.g., 5.1.0 or later stable release).
  5. 5. After upgrade/patch, validate that the XSS vulnerability is remediated by testing that user-supplied input in Web UI fields is properly escaped.
  6. 6. Clear browser caches and test within a trusted session to confirm the fix.
Caveat Review IBM release notes for 5.1.0 or subsequent releases to check for any configuration or compatibility changes that may affect existing integrations or customizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tririga Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11372 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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