Skip to content
Fencer Intel
medium 5.3

CVE-2010-3667 json

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

published 7y ago modified 4mo ago also GHSA-48ww-8h7g-4hwq , EUVD-2022-1618

cvss
5.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist typo3/cms-frontend 4.1.14, 4.2.13, 4.3.4, 4.4.1
  • typo3 typo3 4.1.14, 4.2.13, 4.3.4, 4.4.1

Is CVE-2010-3667 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-3667 updated cvss 5.3

php-typo3-phar-stream-wrapper: allows Spam Abuse in the native form content element

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-frontend
<4.1.14
>=4.2.0, <4.2.13
>=4.3.0, <4.3.4
>=4.4.0, <4.4.1
4.1.14
4.2.13
4.3.4
4.4.1

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.