CVE-2010-3667: TYPO3 is vulnerable to Spam Abuse in the native form content element

CVE-2010-3667 · Severity: low · CVSS 3.1 · Published 2022-04-21

TYPO3 is vulnerable to Spam Abuse in the native form content element

Technologies: typo3/cms-frontend (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2010-3667 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2010-3667 being exploited in the wild.
How severe is CVE-2010-3667?
Low severity, with a CVSS score of 3.1, published 21 April 2022.
Which products and versions are affected?
typo3/cms-frontend (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.14.
Is there a fix for CVE-2010-3667?
Yes. typo3/cms-frontend (Packagist): upgrade to 4.1.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2010-3667?
Check whether you run typo3/cms-frontend (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • typo3/cms-frontend (Packagist): upgrade to 4.1.14 or later
    composer require typo3/cms-frontend:^4.1.14

Affected products

  • typo3/cms-frontend (Packagist) ECOSYSTEM:introduced=0,fixed=4.1.14

Identifiers

  • CVE-2010-3667
  • GHSA-48ww-8h7g-4hwq

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.