CVE-2010-3667: TYPO3 is vulnerable to Spam Abuse in the native form content element
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.
Other sources
TYPO3 is vulnerable to Spam Abuse in the native form content element
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/typo3/cms-frontendto a version that resolves this vulnerability.Fixed in 4.4.1 - Upgrade
Upgrade
composer/typo3/cms-frontendto a version that resolves this vulnerability.Fixed in 4.3.4 - Upgrade
Upgrade
composer/typo3/cms-frontendto a version that resolves this vulnerability.Fixed in 4.2.13 - Upgrade
Upgrade
composer/typo3/cms-frontendto a version that resolves this vulnerability.Fixed in 4.1.14
Event History
Frequently Asked Questions
What is the severity of CVE-2010-3667?
CVE-2010-3667 is considered to have a medium severity due to the potential for spam abuse through the native form content element.
Which TYPO3 versions are affected by CVE-2010-3667?
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.
How do I fix CVE-2010-3667?
To fix CVE-2010-3667, upgrade to TYPO3 versions 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or higher.
What kind of vulnerabilities does CVE-2010-3667 allow attackers to exploit?
CVE-2010-3667 allows attackers to exploit spam abuse in the form content element of TYPO3.
Is there a workaround for CVE-2010-3667?
There is no documented workaround for CVE-2010-3667; the only solution is to upgrade to a secure version.