CVE-2022-41565
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.21 and below, versions 6.0.11 and below and TIBCO Product and Service Catalog powered by TIBCO EBX: versions 1.2.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 confidenceA stored cross-site scripting (XSS) vulnerability exists in the web application component of TIBCO EBX and TIBCO Product and Service Catalog powered by TIBCO EBX. An authenticated attacker with low privileges and network access can inject malicious scripts that persist in the application, affecting other users who view the injected 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.9.22>= 6.0.0, < 6.0.12< 1.2.1CVSS 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 the installed TIBCO EBX versionLocate the EBX installation directory and check the version file or startup logs. Common locations include the installation root folder or check the build/version metadata included with the installation package.Affected if The installed version is less than 5.9.22, or is 6.0.0 through 6.0.11 (inclusive)
-
Identify the installed TIBCO Product and Service Catalog versionIf using Product and Service Catalog, check its version metadata or about/version information within the application interface.Affected if The installed version is less than 1.2.1
-
Confirm web application interface is accessibleAccess the EBX web interface via the configured HTTP/HTTPS endpoint (commonly on port 8080 or 8443) and verify the application is running and reachable.Affected if The web interface is exposed and reachable over the network
-
Verify authentication is enabled for the web interfaceCheck the EBX configuration files (such as web.xml or authentication settings) to confirm that authentication is required to access the application.Affected if Authentication is enabled and low-privilege user accounts can be created or already exist in the system
If the installed TIBCO EBX version is below 5.9.22 or between 6.0.0 and 6.0.11, or Product and Service Catalog is below 1.2.1, and the web interface with authentication is accessible, the environment is likely affected by this stored XSS vulnerability.
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 · scoped1.2.15.9.226.0.12
Apply vendor-provided patches or upgrade to a version beyond the affected releases (TIBCO EBX versions 5.9.22+, 6.0.12+ or TIBCO Product and Service Catalog 1.2.1+). Validate and sanitize all user-supplied input on the server side as an additional defense-in-depth measure.
TIBCO EBX: upgrade to 5.9.22 or 6.0.12; TIBCO Product and Service Catalog powered by TIBCO EBX: upgrade to 1.2.1
- Obtain the TIBCO EBX fixed version (5.9.22 or 6.0.12) or TIBCO Product and Service Catalog powered by TIBCO EBX fixed version (1.2.1) from TIBCO's official support portal or distribution channels
- Review the official TIBCO EBX upgrade documentation for your current version before proceeding
- Test the upgrade in a non-production environment to verify compatibility with your existing configuration and integrations
- Schedule a maintenance window to perform the production upgrade
- Back up your current EBX configuration and data before initiating the upgrade
- Execute the upgrade following TIBCO's documented upgrade procedure for your specific version path
- After upgrade, verify the XSS vulnerability is resolved by attempting to inject malicious scripts through the affected input vectors
- Confirm all existing functionality works as expected in the upgraded environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-41565 — 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-2022-41565 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