# CVE-2022-30577: TIBCO EBX Stored XSS vulnerability

> A low-privileged attacker can inject malicious scripts into TIBCO EBX, potentially compromising user sessions and data upon victim interaction.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Sep 2022
- **Updated:** 22 May 2025
- **Also known as:** GHSA-3qhw-7jqw-3rwp

## What is CVE-2022-30577?

CVE-2022-30577 is a high-severity cross-site scripting vulnerability in TIBCO EBX, published on 21 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Web Server component of TIBCO Software Inc.'s TIBCO EBX contains an easily exploitable vulnerability that allows a low privileged attacker with network access to execute Stored Cross Site Scripting (XSS) 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 EBX: versions 6.0.0 through 6.0.8.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-30577?

It affects 1 product.


Products: Tibco Ebx.

## How do I fix CVE-2022-30577?

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

## Is CVE-2022-30577 being exploited?

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

## Other vulnerabilities in TIBCO EBX

- [CVE-2021-35498](https://insights.sbomify.com/CVE-2021-35498/): TIBCO EBX Insecure Login Mechanism (critical 9.8)
- [CVE-2019-17330](https://insights.sbomify.com/CVE-2019-17330/): TIBCO EBX Exposes Multiple Cross-Site Scripting Vulnerabilities (high 8.8)
- [CVE-2023-26222](https://insights.sbomify.com/CVE-2023-26222/): TIBCO EBX Cross-site Scripting (XXS) Vulnerability (high 8.7)
- [CVE-2022-41565](https://insights.sbomify.com/CVE-2022-41565/): TIBCO EBX Cross Site Scripting (XSS) Vulnerability (high 8.7)
- [CVE-2022-22769](https://insights.sbomify.com/CVE-2022-22769/): TIBCO EBX vulnerabilities (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-30577 and fix it if it is affected.

What it is: CVE-2022-30577 is a high-severity cross-site scripting vulnerability in TIBCO EBX, published on 21 Sep 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-30577 in the wild and no public exploit code.

Affected product: TIBCO EBX. 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-2022-30577/ (Markdown: https://insights.sbomify.com/CVE-2022-30577/index.md)
```

## Sources

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

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