CVE-2021-23273
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 Spotfire client component of TIBCO Software Inc.'s TIBCO Spotfire Analyst, TIBCO Spotfire Analytics Platform for AWS Marketplace, TIBCO Spotfire Desktop, and TIBCO Spotfire Server contains a vulnerability that theoretically allows a low privileged attacker with network access to execute a stored Cross Site Scripting (XSS) attack 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 Spotfire Analyst: versions 10.3.3 and below, versions 10.10.0, 10.10.1, and 10.10.2, versions 10.7.0, 10.8.0, 10.9.0, 11.0.0, and 11.1.0, TIBCO Spotfire Analytics Platform for AWS Marketplace: versions 11.1.0 and below, TIBCO Spotfire Desktop: versions 10.3.3 and below, versions 10.10.0, 10.10.1, and 10.10.2, versions 10.7.0, 10.8.0, 10.9.0, 11.0.0, and 11.1.0, and TIBCO Spotfire Server: versions 10.3.11 and below, versions 10.10.0, 10.10.1, 10.10.2, and 10.10.3, versions 10.7.0, 10.8.0, 10.8.1, 10.9.0, 11.0.0, and 11.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 confidenceStored XSS vulnerability in TIBCO Spotfire client components (Analyst, Desktop, Server, Analytics Platform for AWS Marketplace) allows low-privileged attackers with network access to inject malicious scripts that execute when other users view the affected content. Requires human interaction to trigger.
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<= 11.1.0<= 10.3.3= 10.7.0= 10.8.0= 10.9.0= 10.10.0= 10.10.1= 10.10.2= 11.0.0= 11.1.0<= 10.3.3= 10.7.0= 10.8.0= 10.9.0= 10.10.0= 10.10.1= 10.10.2= 11.0.0= 11.1.0<= 10.3.11= 10.7.0= 10.8.0= 10.8.1= 10.9.0= 10.10.0= 10.10.1= 10.10.2= 10.10.3= 11.0.0= 11.1.0CVSS 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 Spotfire productCheck the installed application name - look for Tibco Analytics Platform, Tibco Spotfire Analyst, Tibco Spotfire Desktop, or Tibco Spotfire Server in the installed programs list or application metadataAffected if Any of these four products are installed
-
Determine the installed version of the productAccess the product's About or Version information panel within the application, or check the installation directory for version metadata filesAffected if The version matches or is within any of the affected ranges: Tibco Analytics Platform <= 11.1.0; Tibco Spotfire Analyst <= 10.3.3 or = 10.7.0/10.8.0/10.9.0/10.10.0/10.10.1/10.10.2/11.0.0/11.1.0; Tibco Spotfire Desktop <= 10.3.3 or = 10.7.0/10.8.0/10.9.0/10.10.0/10.10.1/10.10.2/11.0.0/11.1.0; Tibco S
-
Verify network accessibility of the Spotfire serviceCheck if the Spotfire Server or Analyst/Desktop client is accessible over the network to low-privileged users, or confirm network connectivity settings in the Server configurationAffected if The service is reachable over a network by users who are not administrators
-
Confirm content creation capability for low-privileged usersReview user roles and permissions to determine if non-admin users can upload, create, or modify content such as analysis files, data tables, or visualizations that other users will viewAffected if Low-privileged users can create or modify content that is subsequently viewed by other users
Your environment is affected if you have any of the listed TIBCO Spotfire products installed with a version matching the affected ranges and low-privileged users can create or view shared content over the network.
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.
From vendor dataUpgrade to patched versions (verify with TIBCO). Implement input validation and output encoding on all user-supplied data fields. Apply Content Security Policy (CSP) headers as defense-in-depth.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-23273 — 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-2021-23273 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