CVE-2010-3673 json
TYPO3 is vulnerable to Information Disclosure in the HTML mailing API
published 2019-11-05 7 y ago modified 2026-06-16 4 mo ago also GHSA-5f2f-hr23-j59j , EUVD-2022-1633
- 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 68%
- public exploits
- 0
- none known
Summary
TYPO3 before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows information disclosure in the mail header of the HTML mailing API.
Patch / fix
- packagist typo3/cms-core 4.2.13, 4.3.4, 4.4.1
- typo3 typo3 4.2.13, 4.3.4, 4.4.1
- github.com/TYPO3/typo3@3e24a0f commit
- github.com/TYPO3/typo3@46693d4 commit
- github.com/TYPO3/typo3@a3a62d9 commit
Exploit prediction
1.20% chance of exploitation in the next 30 days, higher than 68% 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:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-core | <4.2.13 >=4.3, <4.3.4 >=4.4, <4.4.1 |
4.2.13 4.3.4 4.4.1 |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
github.com
/TYPO3/typo3/commit/3e24a0fff04897826a12e5cac16b5b0a3848cf2d
web
-
github.com
/TYPO3/typo3/commit/46693d4930d0bce64c5bdd4274224724041cef2f
web
-
github.com
/TYPO3/typo3/commit/a3a62d99507a9e686274306df0cc1c31f4394981
web
-
typo3.org
/security/advisory/typo3-sa-2010-012/#Information_Disclosure
web, vendor-advisory
-
security-tracker.debian.org
/tracker/CVE-2010-3673
web, third-party-advisory
-
bugs.debian.org
/cgi-bin/bugreport.cgi?bug=590719
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2010-3673
advisory
-
github.com
/TYPO3-CMS/core
package
Sources
- CVE List CVE-2010-3673
- GitHub Advisory GHSA-5f2f-hr23-j59j
- NVD CVE-2010-3673
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.