# CVE-2025-3751: TIBCO ActiveMatrix BusinessWorks SQL Injection Vulnerability

> Attackers can perform SQL injection to access unauthorized database information in TIBCO ActiveMatrix BusinessWorks.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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 May 2025
- **Updated:** 21 May 2025
- **Also known as:** GHSA-c49m-468j-4qm9

## What is CVE-2025-3751?

CVE-2025-3751 is a high-severity SQL injection vulnerability in TIBCO ActiveMatrix BusinessWorks, published on 21 May 2025. 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 component listed above contains a vulnerability that can be exploited by an attacker to perform a SQL Injection attack. This could lead to unauthorised access to the database and exposure of sensitive information

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-3751?


## How do I fix CVE-2025-3751?

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

## Is CVE-2025-3751 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3751 and fix it if it is affected.

What it is: CVE-2025-3751 is a high-severity SQL injection vulnerability in TIBCO ActiveMatrix BusinessWorks, published on 21 May 2025. 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-2025-3751 in the wild and no public exploit code.

Affected product: TIBCO ActiveMatrix BusinessWorks. 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-2025-3751/ (Markdown: https://insights.sbomify.com/CVE-2025-3751/index.md)
```

## Sources

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

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