Skip to content
Fencer Intel
high 8.8

CVE-2010-3663 json

TYPO3 Arbitrary Code Execution vulnerability on the backend

published 2019-11-04 7 y ago modified 2026-06-16 4 mo ago also GHSA-wjpc-gjf7-9938 , EUVD-2022-1857

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
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 contains an insecure default value of the variable fileDenyPattern which could allow remote attackers to execute arbitrary code on the backend.

Patch / fix

  • packagist typo3/cms-backend 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

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-3663 updated cvss 8.8

php-typo3-phar-stream-wrapper: insecure default value of fileDenyPattern can lead to code execution on the backend

  • 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

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-backend
<4.1.14
>=4.2, <4.2.13
>=4.3, <4.3.4
>=4.4, <4.4.1
4.1.14
4.2.13
4.3.4
4.4.1

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type

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.