CVE-2023-26222
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 · uneditedThe Web Application component of TIBCO Software Inc.'s TIBCO EBX 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 a stored XSS on the affected system. Affected releases are TIBCO Software Inc.'s TIBCO EBX: versions 5.9.22 and below, versions 6.0.13 and below and TIBCO Product and Service Catalog powered by TIBCO EBX: versions 5.0.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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in the web application component of TIBCO EBX and TIBCO Product and Service Catalog powered by TIBCO EBX. A low-privileged attacker with network access can inject malicious JavaScript or HTML into the application that persists on the server, executing in the browsers of other users who view the compromised content.
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<= 5.0.0>= 5.1.1, < 5.9.23>= 6.0.0, < 6.0.14CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify TIBCO EBX versionAccess the EBX administration console or check the product's 'About' page. The version is typically displayed in the web interface footer or in the admin settings panel. If using command-line, check installation logs or version files in the EBX installation directory.Affected if The installed version falls within <= 5.0.0, >= 5.1.1 and < 5.9.23, or >= 6.0.0 and < 6.0.14.
-
Confirm web application component is enabledVerify that the EBX web interface is accessible by navigating to the application's URL. Check if the HTTP/HTTPS service is running and the web application is exposed.Affected if The web interface is accessible over the network and users can interact with input fields that store data on the server.
-
Check for low-privileged user accessDetermine if the application allows user registration or has low-privileged accounts that can submit content (such as creating records, adding comments, or filling out forms).Affected if Low-privileged or unauthenticated users can submit content that is stored and displayed to other users.
-
Verify patch statusCompare your installed version against the fixed releases: version 5.9.23 or later, or version 6.0.14 or later.Affected if The installed version is earlier than 5.9.23 (for the 5.x branch) or earlier than 6.0.14 (for the 6.x branch).
Your environment is affected if TIBCO EBX or TIBCO Product and Service Catalog is running with a version less than 5.9.23 (for 5.x) or less than 6.0.14 (for 6.x) and the web application component is accessible to users who can submit content.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.9.236.0.14
Apply the vendor patches: upgrade TIBCO EBX to version 5.9.23 or later, or 6.0.14 or later; upgrade TIBCO Product and Service Catalog to a patched version. Additionally, implement output encoding and Content Security Policy headers as defense-in-depth measures.
TIBCO EBX 5.9.23+ or 6.0.14+ (depending on your current major version line); TIBCO Product and Service Catalog: version incorporating fixed EBX component
- 1. Identify the current installed version of TIBCO EBX or TIBCO Product and Service Catalog powered by TIBCO EBX
- 2. For TIBCO EBX 5.x: Upgrade to version 5.9.23 or later
- 3. For TIBCO EBX 6.x: Upgrade to version 6.0.14 or later
- 4. For TIBCO Product and Service Catalog: Upgrade to a version that includes the fixed EBX component (version greater than 5.0.0)
- 5. After upgrade, verify the XSS vulnerability is resolved by testing the web application with a safe XSS test payload in input fields
- 6. Confirm normal application functionality remains intact post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-26222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-26222 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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