CVE-2022-30575
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 Console component of TIBCO Software Inc.'s TIBCO Data Science - Workbench, TIBCO Statistica, TIBCO Statistica - Estore Edition, and TIBCO Statistica Trial contains easily exploitable Reflected Cross Site Scripting (XSS) vulnerabilities that allow a low privileged attacker with network access to execute scripts targeting the affected system or the victim's local system. Affected releases are TIBCO Software Inc.'s TIBCO Data Science - Workbench: versions 14.0.0 and below, TIBCO Statistica: versions 14.0.0 and below, TIBCO Statistica - Estore Edition: versions 14.0.0 and below, and TIBCO Statistica Trial: versions 14.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 confidenceReflected Cross Site Scripting (XSS) vulnerability in the Web Console component of TIBCO Data Science - Workbench, TIBCO Statistica, and related products versions 14.0.0 and below. Allows low-privileged remote attackers to execute arbitrary scripts via unsanitized input reflected in web responses.
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< 14.0.1< 14.0.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 TIBCO product installedLocate the installed TIBCO software on the system. Check Add/Remove Programs (Windows) or the installation directory for the product name. Confirm whether it is TIBCO Data Science - Workbench or TIBCO Statistica.Affected if The product is TIBCO Data Science - Workbench or TIBCO Statistica
-
Check the installed version numberAccess the product version through the Web Console login page footer, the application's Help > About dialog, or check version files in the installation directory. Compare the installed version against 14.0.1.Affected if The installed version is 14.0.0 or below, or any version lower than 14.0.1
-
Confirm Web Console is enabled and accessibleAttempt to access the Web Console via the web interface using the typical port (such as 8080 or 8443) or the URL provided in the product documentation. Verify the login page loads successfully.Affected if Web Console is enabled and reachable on the network
You are affected if you have TIBCO Data Science - Workbench or TIBCO Statistica installed with version 14.0.0 or below and the Web Console is accessible.
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 · scoped14.0.1
Apply vendor-supplied patches for affected TIBCO products. Implement input validation and output encoding for all user-supplied data in the Web Console. Consider deploying Content Security Policy (CSP) headers as defense-in-depth.
TIBCO Data Science - Workbench 14.0.1 or later / TIBCO Statistica 14.0.1 or later
- 1. Back up the current TIBCO Data Science - Workbench or TIBCO Statistica installation and configuration
- 2. Download the updated version (14.0.1 or later) from the official TIBCO support portal at tibco.com
- 3. Stop the TIBCO Web Console service
- 4. Install version 14.0.1 or later following the standard upgrade procedure
- 5. Restore any custom configurations from the backup if needed
- 6. Start the TIBCO Web Console service
- 7. Verify the installation by logging into the Web Console and testing that the previously vulnerable endpoint no longer reflects unsanitized input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30575 — 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-30575 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