Approved changes feed: RSS · Atom
cpe:2.3:a:typo3:typo3_cms:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Typo3 (bebcd01c-0947-5641-89ed-9b814cca944e) |
|---|---|
| Product | Typo3 Cms (9c7d802c-bdca-5e0b-84bb-229474489e45) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-49742 |
vulnerable | 2026-07-29 00:57:45.509717 |
TYPO3 CMS - Broken Access Control in Media Module
Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose sensitive files such as log files. This issue affects TYPO3 CMS versions 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Published: 2026-06-09T10:54:58.139Z
Updated: 2026-06-11T13:27:48.755Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-49741 |
vulnerable | 2026-07-29 00:57:45.509472 |
TYPO3 CMS - Privilege Escalation & SQL Injection in Form Framework
Backend users with write access to the form_definition database table were able to directly create, update, or delete form definition records via DataHandler, bypassing the Form Framework's persistence validation and permission checks. This allowed injecting arbitrary form configurations, re-enabling attack vectors originally addressed in TYPO3-CORE-SA-2018-003, including SQL injection and privilege escalation. This issue affects TYPO3 CMS versions 14.0.0-14.3.2.
Published: 2026-06-09T10:54:19.332Z
Updated: 2026-07-15T12:49:41.979Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-49740 |
vulnerable | 2026-07-29 00:57:45.508898 |
TYPO3 CMS - Insecure Deserialization in Core API
TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry database table) could inject a crafted serialized payload to trigger PHP Object Injection, potentially exploiting a gadget chain to achieve Remote Code Execution or other high-impact effects. Exploiting this vulnerability requires direct local write access to the storage, such as the SQL database or file system. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Published: 2026-06-09T10:53:55.777Z
Updated: 2026-07-15T12:49:15.005Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-49738 |
vulnerable | 2026-07-29 00:57:45.507795 |
TYPO3 CMS - Broken Access Control in File Abstraction Layer
The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Published: 2026-06-09T10:53:31.677Z
Updated: 2026-07-15T12:48:36.417Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47352 |
vulnerable | 2026-07-29 00:55:00.129671 |
TYPO3 CMS - Broken Access Control in Backend API
Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outside their permitted file mounts or storages. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Published: 2026-06-09T10:53:05.815Z
Updated: 2026-07-15T12:47:51.225Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47351 |
vulnerable | 2026-07-29 00:55:00.129420 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47350 |
vulnerable | 2026-07-29 00:55:00.129169 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47349 |
vulnerable | 2026-07-29 00:55:00.128851 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47348 |
vulnerable | 2026-07-29 00:55:00.128435 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47347 |
vulnerable | 2026-07-29 00:55:00.127939 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47346 |
vulnerable | 2026-07-29 00:55:00.127629 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47343 |
vulnerable | 2026-07-29 00:55:00.123939 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-15305 |
vulnerable | 2026-07-29 00:26:17.991707 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-11607 |
vulnerable | 2026-07-29 00:23:31.500835 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-6553 |
vulnerable | 2026-06-08 08:07:04.882418 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-0859 |
vulnerable | 2026-06-08 07:47:13.382201 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59022 |
vulnerable | 2026-06-08 07:35:19.902611 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59021 |
vulnerable | 2026-06-08 07:35:19.901935 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59020 |
vulnerable | 2026-06-08 07:35:19.901507 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59019 |
vulnerable | 2026-06-08 07:35:19.900966 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59018 |
vulnerable | 2026-06-08 07:35:19.900608 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59017 |
vulnerable | 2026-06-08 07:35:19.897013 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59016 |
vulnerable | 2026-06-08 07:35:19.896289 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59015 |
vulnerable | 2026-06-08 07:35:19.895936 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59014 |
vulnerable | 2026-06-08 07:35:19.895376 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-59013 |
vulnerable | 2026-06-08 07:35:19.893943 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15099 |
vulnerable | 2026-06-08 05:19:25.275688 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-15098 |
vulnerable | 2026-06-08 05:19:25.274468 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11069 |
vulnerable | 2026-06-08 05:16:36.390601 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11067 |
vulnerable | 2026-06-08 05:16:36.387502 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11066 |
vulnerable | 2026-06-08 05:16:36.387159 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11065 |
vulnerable | 2026-06-08 05:16:36.386772 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11064 |
vulnerable | 2026-06-08 05:16:36.385442 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-11063 |
vulnerable | 2026-06-08 05:16:36.383289 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.