CVE-2009-3631 json
TYPO3 Backend Command Injection via Shell Metacharacters in Uploaded File Name
published 2009-11-02 17 y ago modified 2026-06-16 4 mo ago also GHSA-3cqw-pxgr-jhrm , EUVD-2022-2162
- cvss
- 8.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
The Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2, when the DAM extension or ftp upload is enabled, allows remote authenticated users to execute arbitrary commands via shell metacharacters in a filename.
Patch / fix
- packagist typo3/cms-backend 4.1.13, 4.2.10, 4.3beta2
Exploit prediction
2.94% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 8.5 | AV:N/AC:M/Au:S/C:C/I:C/A:C |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-backend | <=4.0.13 >=4.1.0, <4.1.13 >=4.2.0, <4.2.10 >=4.3alpha1, <4.3beta2 |
4.1.13 4.2.10 4.3beta2 |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
-
typo3.org
/teams/security/security-bulletins/typo3-sa-2009-016/
patch, vendor-advisory
-
vupen.com
/english/advisories/2009/3009
vdb-entry, patch, vendor-advisory
-
securityfocus.com
/bid/36801
vdb-entry, patch
-
secunia.com
/advisories/37122
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/53923
vdb-entry, web
-
marc.info
/?l=oss-security&m=125632856206736&w=2
mailing-list, web
-
nvd.nist.gov
/vuln/detail/CVE-2009-3631
advisory
-
github.com
/TYPO3-CMS/backend
package
-
web.archive.org
/web/20101223093042/http://www.securityfocus.com/bid/36801
web
-
typo3.org
/teams/security/security-bulletins/typo3-sa-2009-016
web
Sources
- CVE List CVE-2009-3631
- GitHub Advisory GHSA-3cqw-pxgr-jhrm
- NVD CVE-2009-3631
Fencer Vulns 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.