# CVE-2026-44331: SQL injection in ProFTPD

> Remote attackers can inject SQL commands via crafted domain names in ProFTPD when reverse DNS is enabled, potentially compromising database integrity.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** Yes
- **Published:** 5 May 2026
- **Updated:** 6 May 2026
- **Also known as:** DEBIAN-CVE-2026-44331, GHSA-jmg2-v72j-gmvc, OESA-2026-2265, OESA-2026-2267, OESA-2026-2268, UBUNTU-CVE-2026-44331

## What is CVE-2026-44331?

CVE-2026-44331 is a high-severity SQL injection vulnerability in ProFTPD, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In ProFTPD through 1.3.9a before 7666224, a SQL injection vulnerability in sqltab_fetch_clients_cb() in contrib/mod_wrap2_sql.c allows a remote attacker to inject arbitrary SQL commands via a crafted domain name that is accessed in a reverse DNS lookup. When "UseReverseDNS on" is enabled, the attacker-supplied hostname is passed unescaped into SQL queries. The character restrictions of DNS names may affect exploitability.

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

## Which versions are affected by CVE-2026-44331?


## How do I fix CVE-2026-44331?

Apply the vendor's patch.

## Is CVE-2026-44331 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44331 and fix it if it is affected.

What it is: CVE-2026-44331 is a high-severity SQL injection vulnerability in ProFTPD, published on 5 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44331 in the wild and no public exploit code.

Affected product: ProFTPD. 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-2026-44331/ (Markdown: https://insights.sbomify.com/CVE-2026-44331/index.md)
```

## Sources

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

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