# CVE-2024-22719: SQL injection in n/a

> Attackers can execute arbitrary SQL commands via the client search keyword field in Form Tools, potentially accessing or modifying database contents.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2024
- **Updated:** 7 Nov 2024
- **Also known as:** GHSA-f722-mp6c-4849

## What is CVE-2024-22719?

CVE-2024-22719 is a high-severity SQL injection vulnerability in n/a, published on 11 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL Injection vulnerability in Form Tools 3.1.1 allows attackers to run arbitrary SQL commands via the 'keyword' when searching for a client.

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

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

It affects 1 product.


Products: Formtools Form Tools.

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

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

## Is CVE-2024-22719 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-22718](https://insights.sbomify.com/CVE-2024-22718/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2024-22722](https://insights.sbomify.com/CVE-2024-22722/): Code injection in n/a (high 7.2)
- [CVE-2024-22721](https://insights.sbomify.com/CVE-2024-22721/): Cross-site request forgery in n/a (medium 6.3)
- [CVE-2024-22717](https://insights.sbomify.com/CVE-2024-22717/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-22637](https://insights.sbomify.com/CVE-2024-22637/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22719 is a high-severity SQL injection vulnerability in n/a, published on 11 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22719 exists.

Affected product: n/a. 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-22719/ (Markdown: https://insights.sbomify.com/CVE-2024-22719/index.md)
```

## Sources

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

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