First published: Mon Nov 04 2019(Updated: )
TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows Spam Abuse in the native form content element.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/typo3/cms-frontend | >=4.4.0<4.4.1 | 4.4.1 |
composer/typo3/cms-frontend | >=4.3.0<4.3.4 | 4.3.4 |
composer/typo3/cms-frontend | >=4.2.0<4.2.13 | 4.2.13 |
composer/typo3/cms-frontend | <4.1.14 | 4.1.14 |
debian/typo3-src | ||
Typo3 Typo3 | >=4.4.0<4.4.1 | |
Typo3 Typo3 | >=4.3.0<4.3.4 | |
Typo3 Typo3 | <4.1.14 | |
Typo3 Typo3 | >=4.2.0<4.2.13 | |
TYPO3 | <4.1.14 | |
TYPO3 | >=4.2.0<4.2.13 | |
TYPO3 | >=4.3.0<4.3.4 | |
TYPO3 | >=4.4.0<4.4.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-3667 is considered to have a medium severity due to the potential for spam abuse through the native form content element.
CVE-2010-3667 affects TYPO3 versions before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4, and 4.4.x before 4.4.1.
To fix CVE-2010-3667, upgrade to TYPO3 versions 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or higher.
CVE-2010-3667 allows attackers to exploit spam abuse in the form content element of TYPO3.
There is no documented workaround for CVE-2010-3667; the only solution is to upgrade to a secure version.