CVE-2019-8991
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 administrator web interface of TIBCO Software Inc.'s TIBCO ActiveMatrix BPM, TIBCO ActiveMatrix BPM Distribution for TIBCO Silver Fabric, TIBCO ActiveMatrix Policy Director, TIBCO ActiveMatrix Service Bus, TIBCO ActiveMatrix Service Grid, TIBCO Silver Fabric Enabler for ActiveMatrix BPM, and TIBCO Silver Fabric Enabler for ActiveMatrix Service Grid contains multiple vulnerabilities that may allow for cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks. Affected releases are TIBCO Software Inc.'s TIBCO ActiveMatrix BPM: versions up to and including 4.2.0, TIBCO ActiveMatrix BPM Distribution for TIBCO Silver Fabric: versions up to and including 4.2.0, TIBCO ActiveMatrix Policy Director: versions up to and including 1.1.0, TIBCO ActiveMatrix Service Bus: versions up to and including 3.3.0, TIBCO ActiveMatrix Service Grid: versions up to and including 3.3.1, TIBCO Silver Fabric Enabler for ActiveMatrix BPM: versions up to and including 1.4.1, and TIBCO Silver Fabric Enabler for ActiveMatrix Service Grid: versions up to and including 1.3.1.
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 confidenceThe administrator web interface of multiple TIBCO ActiveMatrix products contains vulnerabilities allowing cross-site scripting (XSS) and cross-site request forgery (CSRF) attacks due to insufficient input validation and lack of anti-CSRF protections in the web 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<= 4.2.0<= 1.1.0<= 3.3.0<= 3.3.0<= 3.3.1<= 1.3.1<= 1.4.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 ActiveMatrix productReview installed software or check for TIBCO ActiveMatrix components on the system. Common installation directories include TIBCO home folders (e.g., TIBCO_HOME or C:\TIBCO). Look for product names: Activematrix BPM, Activematrix Policy Director, Activematrix Service Bus, Activematrix Service Grid, or Silver Fabric Enabler.Affected if Any of these five products are installed
-
Determine installed product versionLocate the version information for the installed TIBCO product. Check product-specific README files, version.info files, or the manifest/registry entries within the product installation directory. Version information is typically found in the product's root folder or within the /bin directory.Affected if Version is at or below the affected threshold: BPM <=4.2.0, Policy Director <=1.1.0, Service Bus <=3.3.0, Service Grid <=3.3.0 or <=3.3.1, Silver Fabric Enabler <=1.3.1 or <=1.4.1
-
Verify admin web interface is enabledCheck the product configuration files (such as domain.xml, config.ini, or similar) for web interface settings. Look for configuration entries that enable or expose the administrator console, typically on ports 8080, 8443, or custom admin ports. Consult product documentation for admin interface configuration location.Affected if The administrator web interface is enabled and accessible on any network interface
-
Confirm web interface is network-reachableReview network binding configuration and firewall rules to determine if the admin web interface port is exposed to network users. Check if the interface binds to 0.0.0.0 or a non-localhost address.Affected if The admin web interface is reachable from network segments beyond localhost
If a TIBCO ActiveMatrix product from the affected list is installed with a version at or below the specified threshold and its admin web interface is enabled and accessible, the environment is vulnerable to CVE-2019-8991 XSS and CSRF attacks.
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 dataApply vendor-provided patches/updates to upgrade affected TIBCO ActiveMatrix products to patched versions; implement input validation and anti-CSRF tokens as compensating controls until patches can be applied.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8991 — 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-2019-8991 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