# CVE-2019-8991: Cross-site scripting in TIBCO ActiveMatrix BPM

> Attackers can execute cross-site scripting and request forgery attacks in the TIBCO ActiveMatrix administrator interface, potentially compromising user accounts.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-92ph-vwr5-g5f4

## What is CVE-2019-8991?

CVE-2019-8991 is a high-severity cross-site scripting vulnerability in TIBCO ActiveMatrix BPM, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-8991?

It affects 5 products.


Products: Tibco Activematrix Bpm, Tibco Activematrix Policy Director, Tibco Activematrix Service Bus, Tibco Activematrix Service Grid, Tibco Silver Fabric Enabler.

## How do I fix CVE-2019-8991?

No fix has been published for CVE-2019-8991 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-8991 being exploited?

There is no known exploitation of CVE-2019-8991 in the wild and no public exploit code.

## Other vulnerabilities in TIBCO ActiveMatrix BPM

- [CVE-2019-8992](https://insights.sbomify.com/CVE-2019-8992/): TIBCO Active Matrix Service Grid Administrator Remote Code Execution (critical 9.9)
- [CVE-2010-4495](https://insights.sbomify.com/CVE-2010-4495/): Code injection in n/a (critical 9.0)
- [CVE-2019-8993](https://insights.sbomify.com/CVE-2019-8993/): TIBCO Active Matrix Service Grid Administrator Unauthenticated Download of Sensitive File (high 8.6)
- [CVE-2012-0687](https://insights.sbomify.com/CVE-2012-0687/): Information disclosure in n/a (medium 5.0)
- [CVE-2012-0689](https://insights.sbomify.com/CVE-2012-0689/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8991 and fix it if it is affected.

What it is: CVE-2019-8991 is a high-severity cross-site scripting vulnerability in TIBCO ActiveMatrix BPM, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-8991 in the wild and no public exploit code.

Affected product: TIBCO ActiveMatrix BPM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-8991/ (Markdown: https://insights.sbomify.com/CVE-2019-8991/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-8991
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-8991
- OSV: https://osv.dev/vulnerability/CVE-2019-8991

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-8991/
Summaries are generated and may contain mistakes; the official description above is the record.