# CVE-2019-16682: url_redirect for Typo3 SQLi Vulnerability

> An attacker can execute arbitrary SQL commands via the url_redirect extension in TYPO3, potentially reading or modifying database contents.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hcpv-xh8q-f3vq

## What is CVE-2019-16682?

CVE-2019-16682 is a high-severity SQL injection vulnerability in n/a, published on 16 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The url_redirect (aka URL redirect) extension through 1.2.1 for TYPO3 fails to properly sanitize user input and is susceptible to SQL Injection.

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

## Which versions are affected by CVE-2019-16682?

2 open source packages ship an affected version, including sfroemken/url_redirect. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sfroemken/url_redirect` | Packagist | All versions | 1.2.2 |
| `sfroemken/url_redirect` | Packagist | All versions | 1.2.2 |

Products: Url Redirect Project Url Redirect.

## How do I fix CVE-2019-16682?

Upgrade sfroemken/url_redirect to 1.2.2 or later.

## Is CVE-2019-16682 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16682 and fix it if it is affected.

What it is: CVE-2019-16682 is a high-severity SQL injection vulnerability in n/a, published on 16 Oct 2019. 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-2019-16682 in the wild and no public exploit code.

Affected packages and fixed versions:
- sfroemken/url_redirect (Packagist): affected all versions; fixed in 1.2.2
- sfroemken/url_redirect (Packagist): affected all versions; fixed in 1.2.2

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-2019-16682/ (Markdown: https://insights.sbomify.com/CVE-2019-16682/index.md)
```

## Sources

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

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