CVE-2021-31777 json
SQL Injection in t3/dce
published 2021-04-28 5 y ago modified 2026-06-17 4 mo ago also GHSA-5v5h-4w2g-gxxc , EUVD-2021-1272
- cvss
- 4.9
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
The dce (aka Dynamic Content Element) extension 2.2.0 through 2.6.x before 2.6.2, and 2.7.x before 2.7.1, for TYPO3 allows SQL Injection via a backend user account.
Patch / fix
- packagist t3/dce 2.6.2
- dynamic_content_elements_project dynamic_content_elements 2.6.2, 2.7.1
Exploit prediction
1.41% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/162429/TYPO3-6.2.1-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
| GitHub | 3.1 | 7.6 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | t3/dce | >=2.2.0, <2.6.2 |
2.6.2 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
typo3.org
/security/advisory/typo3-ext-sa-2021-005
web, patch, third-party-advisory
-
bitbucket.org
/ArminVieweg/dce/commits/998a2392f69f2153797c5ace6e8914ca309e70c7
web
-
packetstormsecurity.com
/files/162429/TYPO3-6.2.1-SQL-Injection.html
web, exploit, third-party-advisory
-
excellium-services.com
/cert-xlm-advisory/
not-applicable
- cds.thalesgroup.com /en/tcs-cert/CVE-2021-31777
-
nvd.nist.gov
/vuln/detail/CVE-2021-31777
advisory
-
excellium-services.com
/cert-xlm-advisory
web
-
packagist.org
/packages/t3/dce
web
Sources
- CVE List CVE-2021-31777
- GitHub Advisory GHSA-5v5h-4w2g-gxxc
- NVD CVE-2021-31777
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.