# CVE-2024-5276: SQL Injection Vulnerability in FileCatalyst Workflow 5.1.6 Build 135 (and earlier)

> An attacker can modify application data and potentially create admin users via SQL injection in FileCatalyst Workflow, especially if anonymous access is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-mgcv-6r68-pw73

## What is CVE-2024-5276?

CVE-2024-5276 is a critical SQL injection vulnerability in Fortra FileCatalyst Workflow, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL Injection vulnerability in Fortra FileCatalyst Workflow allows an attacker to modify application data.  Likely impacts include creation of administrative users and deletion or modification of data in the application database. Data exfiltration via SQL injection is not possible using this vulnerability. Successful unauthenticated exploitation requires a Workflow system with anonymous access enabled, otherwise an authenticated user is required. This issue affects all versions of FileCatalyst Workflow from 5.1.6 Build 135 and earlier.

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

## Which versions are affected by CVE-2024-5276?

It affects 1 product.


Products: Fortra Filecatalyst Workflow.

## How do I fix CVE-2024-5276?

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

## Is CVE-2024-5276 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5276 exists.

Public exploit code:

- Fortra FileCatalyst Workflow SQL Injection (CVE-2024-5276) (metasploit)
- Fortra FileCatalyst Workflow <= v5.1.6 - SQL Injection (nuclei): http/cves/2024/CVE-2024-5276.yaml

## Other vulnerabilities in Fortra FileCatalyst Workflow

- [CVE-2024-6633](https://insights.sbomify.com/CVE-2024-6633/): Insecure Default in FileCatalyst Workflow 5.1.6 Build 139 (and earlier) (critical 9.8)
- [CVE-2024-25153](https://insights.sbomify.com/CVE-2024-25153/): Remote Code Execution in FileCatalyst Workflow 5.x prior to 5.1.6 Build 114 (critical 9.8)
- [CVE-2024-6632](https://insights.sbomify.com/CVE-2024-6632/): SQL Injection in FileCatalyst Workflow 5.1.6 Build 139 (and earlier) (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-5276 and fix it if it is affected.

What it is: CVE-2024-5276 is a critical SQL injection vulnerability in Fortra FileCatalyst Workflow, published on 25 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-5276 exists.

Affected product: Fortra FileCatalyst Workflow. 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-2024-5276/ (Markdown: https://insights.sbomify.com/CVE-2024-5276/index.md)
```

## Sources

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

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