url_redirect for Typo3 SQLi Vulnerability
CVE-2019-16682GHSA-hcpv-xh8q-f3vq
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (sfroemken/url_redirect 1.2.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist sfroemken/url_redirect
- Affected
- <= 1.2.1
- Fixed in
- 1.2.2
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hcpv-xh8q-f3vq lists affected ranges: Packagist sfroemken/url_redirect >=0 <=1.2.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
- EPSS
- CVE-2019-16682: 0.82% estimated exploitation activity in the next 30 days; percentile 57.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
The urlredirect (aka URL redirect) extension through 1.2.1 for TYPO3 fails to properly sanitize user input and is susceptible to SQL Injection.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-hcpv-xh8q-f3vq
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2019-16682 Advisory: url_redirect for Typo3 SQLi Vulnerability IDs: CVE-2019-16682, GHSA-hcpv-xh8q-f3vq Record: https://patchnext.com/advisories/cve-2019-16682 (revision 1, source checked 26 Oct 2026, 14:09 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: sfroemken/url_redirect 1.2.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist sfroemken/url_redirect: affected <= 1.2.1; fixed in 1.2.2 ## Suggested inspection (read-only) - Packagist sfroemken/url_redirect: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on sfroemken/url_redirect. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-hcpv-xh8q-f3vq (GitHub-reviewed advisory GHSA-hcpv-xh8q-f3vq lists affected ranges: Packagist sfroemken/url_redirect >=0 <=1.2.1) Commands are suggestions: review each one before running it.
Loading voting…