dbcve.org
EbxApplication · Tibco

CVE-2022-22769

CRITICAL · 9.0 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to 1.2.0 / 3.20.19 or later.
See remediation →
94/100
Remediation priority · Urgent
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
The Web server component of TIBCO Software Inc.'s TIBCO EBX, TIBCO EBX, TIBCO EBX, TIBCO EBX Add-ons, TIBCO EBX Add-ons, TIBCO EBX Add-ons, and TIBCO Product and Service Catalog powered by TIBCO EBX contains an easily exploitable vulnerability that allows a low privileged attacker with network access to execute Stored Cross Site Scripting (XSS) on the affected system. A successful attack using this vulnerability requires human interaction from a person other than the attacker. Affected releases are TIBCO Software Inc.'s TIBCO EBX: versions 5.8.124 and below, TIBCO EBX: versions 5.9.3, 5.9.4, 5.9.5, 5.9.6, 5.9.7, 5.9.8, 5.9.9, 5.9.10, 5.9.11, 5.9.12, 5.9.13, 5.9.14, and 5.9.15, TIBCO EBX: versions 6.0.0, 6.0.1, 6.0.2, and 6.0.3, TIBCO EBX Add-ons: versions 3.20.18 and below, TIBCO EBX Add-ons: versions 4.1.0, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.5.0, 4.5.1, 4.5.2, 4.5.3, 4.5.4, 4.5.5, and 4.5.6, TIBCO EBX Add-ons: versions 5.0.0, 5.0.1, 5.1.0, 5.1.1, and 5.2.0, and TIBCO Product and Service Catalog powered by TIBCO EBX: versions 1.1.0 and below.

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

Stored Cross-Site Scripting (XSS) vulnerability in TIBCO EBX web server component allowing low-privileged attackers to inject malicious scripts that execute in browsers of other users who access the compromised data.

MitigationApply vendor-supplied patches for affected TIBCO EBX versions; implement output encoding and input validation as interim controls if immediate patching is not feasible.

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
EbxApplication
Affected:< 5.8.125= 5.9.3= 5.9.4= 5.9.5= 5.9.6= 5.9.7= 5.9.8= 5.9.9= 5.9.10= 5.9.11= 5.9.12= 5.9.13
Ebx Add OnsPlugin / extension
Affected:< 3.20.19= 4.1.0= 4.2.0= 4.2.1= 4.2.2= 4.3.0= 4.3.1= 4.3.2= 4.3.3= 4.3.4= 4.4.0= 4.4.1
Product And Service Catalog Powered By Tibco EbxApplication
Affected:< 1.2.0

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
High
Integrity
High
Availability
High

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

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. Identify TIBCO EBX version
    Locate the EBX installation directory and check the version file or product metadata. Common locations: check the product version in the EBX administration console, or look for version info in the installation logs or configuration files under the EBX home directory.
    Affected if The installed version matches any of the following: < 5.8.125; = 5.9.3; = 5.9.4; = 5.9.5; = 5.9.6; = 5.9.7; = 5.9.8; = 5.9.9; = 5.9.10; = 5.9.11; = 5.9.12; = 5.9.13
  2. Identify TIBCO EBX Add Ons version
    Check the installed version of any EBX add-on components. This is typically visible in the EBX administration interface under Add-Ons management, or documented in the add-on's own version file.
    Affected if The add-on version matches any of the following: < 3.20.19; = 4.1.0; = 4.2.0; = 4.2.1; = 4.2.2; = 4.3.0; = 4.3.1; = 4.3.2; = 4.3.3; = 4.3.4; = 4.4.0; = 4.4.1
  3. Check for TIBCO Product and Service Catalog component
    Identify if the TIBCO Product and Service Catalog powered by TIBCO EBX is installed. Check the component version through the EBX administration console or the component's own metadata.
    Affected if The Product and Service Catalog component version is less than 1.2.0
  4. Confirm web server component exposure
    Verify that the EBX web server component is accessible. This is typically exposed on port 8080, 8443, or a custom configured port. Check network listeners and firewall rules to determine if the web interface is reachable from user networks.
    Affected if The EBX web interface is accessible to users over the network, particularly low-privileged users who can input data into the system

You are affected if your installed TIBCO EBX version, EBX Add Ons version, or Product and Service Catalog version falls within the affected ranges AND the web server component is accessible 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
Upgrade available Upgrade to 1.2.0 / 3.20.19 / 5.8.125 or later
Fixed in 1.2.03.20.195.8.125
Interim mitigation

Apply vendor-supplied patches for affected TIBCO EBX versions; implement output encoding and input validation as interim controls if immediate patching is not feasible.

Recommended fix Moderate confidence

TIBCO EBX 5.8.125 or later / 5.9.16 or later / 6.0.4 or later; TIBCO EBX Add-ons 3.20.19 or later / 4.5.7 or later / 5.2.1 or later; TIBCO Product and Service Catalog 1.2.0 or later

  1. 1. Identify the current installed version of TIBCO EBX, TIBCO EBX Add-ons, or TIBCO Product and Service Catalog powered by TIBCO EBX by checking the product documentation or administration console.
  2. 2. For TIBCO EBX: If running version 5.8.124 or below, upgrade to version 5.8.125 or later. If running version 5.9.3, 5.9.4, 5.9.5, 5.9.6, 5.9.7, 5.9.8, 5.9.9, 5.9.10, 5.9.11, 5.9.12, 5.9.13, 5.9.14, or 5.9.15, upgrade to a version after 5.9.15 (such as 5.9.16 or later). If running version 6.0.0, 6.0.1, 6.0.2, or 6.0.3, upgrade to a version after 6.0.3 (such as 6.0.4 or later).
  3. 3. For TIBCO EBX Add-ons: If running version 3.20.18 or below, upgrade to version 3.20.19 or later. If running version 4.1.0, 4.2.0, 4.2.1, 4.2.2, 4.3.0, 4.3.1, 4.3.2, 4.3.3, 4.3.4, 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.5.0, 4.5.1, 4.5.2, 4.5.3, 4.5.4, 4.5.5, or 4.5.6, upgrade to a version after 4.5.6. If running version 5.0.0, 5.0.1, 5.1.0, 5.1.1, or 5.2.0, upgrade to a version after 5.2.0.
  4. 4. For TIBCO Product and Service Catalog powered by TIBCO EBX: If running version 1.1.0 or below, upgrade to version 1.2.0 or later.
  5. 5. Download the appropriate fixed version from TIBCO's official support portal at tibco.com and follow the standard upgrade procedure documented in the product installation guide.
  6. 6. After upgrading, verify that the Stored XSS vulnerability is remediated by reviewing release notes or patch documentation for the new version.
Caveat Review TIBCO release notes for compatibility notes and any breaking changes between your current version and the target upgrade version before proceeding.

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

Fix this in Ebx Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22769 — 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-2022-22769 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