NimbusApplication · Tibco

CVE-2021-35499

MEDIUM · 5.4 CVSS v3.1 Published 2021-10-26
Fix available
A fix is available. Upgrade to after 10.4.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The Web Reporting component of TIBCO Software Inc.'s TIBCO Nimbus contains easily exploitable Stored Cross Site Scripting (XSS) vulnerabilities that allow a low privileged attacker to social engineer a legitimate user with network access to execute scripts targeting the affected system or the victim's local 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 Nimbus: versions 10.4.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 confidence

TIBCO Nimbus Web Reporting component contains a stored Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected and persistently stored. A low-privileged attacker with network access can exploit this by social engineering a legitimate user to trigger the stored payload, potentially executing scripts against the affected system or the victim's local browser.

MitigationUpgrade TIBCO Nimbus to a version above 10.4.0. Additionally, implement robust input validation and output encoding in the Web Reporting component to neutralize XSS vectors.

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
NimbusApplication
Affected:<= 10.4.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TIBCO Nimbus version
    Check the Nimbus application version through the admin console, installation directory metadata, or product about information. Common locations: <Nimbus_install>/version.txt or within the Nimbus Control/Admin UI.
    Affected if The installed version is 10.4.0 or lower.
  2. Confirm Web Reporting component is enabled
    Access Nimbus admin interface and navigate to the Web Reporting module configuration. Verify if the Web Reporting feature is active and accessible to users.
    Affected if Web Reporting component is enabled and accessible to low-privileged users.
  3. Inspect Web Reporting data storage
    Examine the database or file storage used by the Web Reporting component for any unexpected or suspicious content in report definitions, templates, or user-generated fields that could contain stored XSS payloads.
    Affected if Unexpected script tags, JavaScript code, or HTML elements are found stored in Web Reporting data fields.
  4. Review web access logs for XSS patterns
    Analyze HTTP access logs from the Nimbus web server for unusual request patterns containing script tags, javascript: URIs, or other XSS vectors in Web Reporting input fields.
    Affected if Log entries show repeated XSS attack patterns being submitted to Web Reporting endpoints.

Your environment is affected if TIBCO Nimbus version is 10.4.0 or lower AND the Web Reporting component is enabled and accessible to users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 10.4.0
Interim mitigation

Upgrade TIBCO Nimbus to a version above 10.4.0. Additionally, implement robust input validation and output encoding in the Web Reporting component to neutralize XSS vectors.

Fix this in Nimbus Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-35499 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-35499 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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