CVE-2022-30576
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 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 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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in the Web Console component of TIBCO Data Science - Workbench, TIBCO Statistica, and related products. A low-privileged attacker with network access can inject malicious scripts that persist on the server and execute in the browsers of other users who access the affected interface.
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 installed TIBCO product and versionCheck the installed version of TIBCO Data Science Workbench or TIBCO Statistica using the product's built-in version check, typically available in the product UI under Help > About, or check the installation directory for version manifest files.Affected if The installed version is TIBCO Data Science Workbench or TIBCO Statistica with version less than 14.0.1
-
Confirm Web Console component is accessibleVerify whether the Web Console interface is enabled and accessible by attempting to reach the web-based administration interface, typically on ports 8080 or 8443, or checking the product configuration for Web Console enablement settings.Affected if The Web Console component is enabled and accessible to network users
-
Check for existing XSS payloads in the applicationReview application logs, user input fields, or stored configuration within the Web Console for any suspicious script tags or HTML attributes that may indicate prior exploitation of stored XSS.Affected if Malicious script content is found stored in the Web Console application data or logs
A user is affected if they have TIBCO Data Science Workbench or TIBCO Statistica installed with version less than 14.0.1 and the Web Console component is enabled and 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-provided patches when available. Implement output encoding and input validation for all user-supplied data rendered in the Web Console. Since the description indicates human interaction is required, user awareness training complements technical remediation.
14.0.1
- Upgrade TIBCO Data Science - Workbench to version 14.0.1 or later
- Upgrade TIBCO Statistica to version 14.0.1 or later
- Upgrade TIBCO Statistica - Estore Edition to version 14.0.1 or later
- Upgrade TIBCO Statistica Trial to version 14.0.1 or later
- After upgrade, verify the Web Console component no longer accepts unsanitized input that could execute XSS attacks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30576 — 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-30576 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