CVE intelligence and bounded remediation
CVE-2021-23273 — Tibco Analytics Platform security vulnerability
The 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.
- Severity
- High
- CVSS
- 8 (3.1)
- Published
- 2021-03-09
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-79
Affected products
- tibco / analytics_platform
- tibco / spotfire_analyst
- tibco / spotfire_analyst / 10.7.0
- tibco / spotfire_analyst / 10.8.0
- tibco / spotfire_analyst / 10.9.0
- tibco / spotfire_analyst / 10.10.0
Matched remediation archetype
Cross-site scripting and unsafe browser output
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
- Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
- Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.
Remediate safely
- Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
- Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
- Update affected rendering components and add tests for every output context using inert sentinel markup.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.