CVE-2011-3583
It was found that Typo3 Core versions 4.5.0 - 4.5.5 uses prepared statements that, if the parameter values are not properly replaced, could lead to a SQL Injection vulnerability.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.37%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
It was found that Typo3 Core versions 4.5.0 - 4.5.5 uses prepared statements that, if the parameter values are not properly replaced, could lead to a SQL Injection vulnerability. This issue can only be exploited if two or more parameters are bound to the query and at least two come from user input.
- CVSS 3.1
- 9.8 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 1.37% probability · 70th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-89
- Affected
- typo3/typo3
- Source
- secalert@redhat.com
References
- https://access.redhat.com/security/cve/cve-2011-3583Broken Link
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641682Third Party Advisory
- https://security-tracker.debian.org/tracker/CVE-2011-3583Third Party Advisory
- https://typo3.org/security/advisory/typo3-core-sa-2011-002/Vendor Advisory
- https://access.redhat.com/security/cve/cve-2011-3583Broken Link
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641682Third Party Advisory
- https://security-tracker.debian.org/tracker/CVE-2011-3583Third Party Advisory
- https://typo3.org/security/advisory/typo3-core-sa-2011-002/Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.