dbcve.org
Ebx Add OnsPlugin / extension · Tibco

CVE-2023-26217

HIGH · 8.8 CVSS v3.1 Published 2023-07-19
Fix available
A fix is available. Upgrade to after 5.6.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Data Exchange Add-on component of TIBCO Software Inc.'s TIBCO EBX Add-ons contains an easily exploitable vulnerability that allows a low privileged user with import permissions and network access to the EBX server to execute arbitrary SQL statements on the affected system. Affected releases are TIBCO Software Inc.'s TIBCO EBX Add-ons: versions 4.5.17 and below, versions 5.6.2 and below, version 6.1.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 confidence

A SQL injection vulnerability in the Data Exchange Add-on of TIBCO EBX allows authenticated users with import permissions to execute arbitrary SQL statements on the underlying database. The attacker requires only network access to the EBX server and low-privileged user credentials with import permissions.

MitigationUpgrade TIBCO EBX Add-ons to a patched version beyond 4.5.17, 5.6.2, and 6.1.0 as specified by vendor advisories. Until patched, restrict network access to the EBX server and limit import permissions to only essential personnel.

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
Ebx Add OnsPlugin / extension
Affected:<= 4.5.17>= 5.0.0, <= 5.6.2= 6.1.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 installation and version
    Locate the EBX installation directory and check the version file (typically in the installation root or in the productVersion.properties file). Alternatively, access the EBX web interface and check the About or Administration section for the version number.
    Affected if The installed version falls within the affected ranges: <= 4.5.17, 5.0.0-5.6.2, or 6.1.0.
  2. Confirm Data Exchange Add-on is present
    Check the EBX installation for the Data Exchange Add-on component. This is typically found in the add-ons or plugins directory, or can be verified through the EBX Administration interface under Add-ons or Features.
    Affected if The Data Exchange Add-on is installed and enabled on the EBX server.
  3. Verify import permissions configuration
    Access EBX Administration and navigate to User Management or Security settings. Review which users or roles have import permissions granted, specifically for the Data Exchange functionality.
    Affected if Any user account (including low-privileged accounts) has import permissions enabled in the EBX security configuration.
  4. Check network accessibility of EBX server
    Determine if the EBX web interface is accessible from the network by testing HTTP/HTTPS connectivity to the EBX server port from untrusted networks.
    Affected if The EBX server is accessible over the network to users who should not have access or from untrusted network segments.

The environment is affected if TIBCO EBX with Data Exchange Add-on is installed at a version within 4.5.17, 5.0.0-5.6.2, or 6.1.0, and import permissions are granted to any user with network access.

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 a release after 5.6.2
Interim mitigation

Upgrade TIBCO EBX Add-ons to a patched version beyond 4.5.17, 5.6.2, and 6.1.0 as specified by vendor advisories. Until patched, restrict network access to the EBX server and limit import permissions to only essential personnel.

Recommended fix Moderate confidence

TIBCO EBX Add-ons: 4.5.18+ (for 4.x branch), 5.6.3+ (for 5.x branch), 6.1.1+ (for 6.x branch)

  1. 1. Identify the currently installed TIBCO EBX Add-ons version by checking the product documentation or system inventory
  2. 2. For version 4.5.x: Upgrade to version 4.5.18 or later
  3. 3. For version 5.0.x through 5.6.x: Upgrade to version 5.6.3 or later
  4. 4. For version 6.1.0: Upgrade to version 6.1.1 or later
  5. 5. After upgrade, verify the SQL injection vulnerability is no longer present by reviewing TIBCO security advisories
  6. 6. Test the Data Exchange Add-on functionality to ensure the upgrade did not break existing workflows
  7. 7. Review user permissions for the import functionality to ensure only necessary users retain these privileges
Caveat Standard upgrade risks apply; test in non-production environment first

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

Fix this in Ebx Add Ons Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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