ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. When processing images, TYPO3 determined the coder from the file type detected by the file contents, as long as the detected mime-type started with image/. A file containing MVG (Magick Vector Graphics) instructions, uploaded with an image file extension like .png, was therefore processed with the MVG coder. MVG instructions can read local files into the processed image, which allows disclosing the contents of arbitrary files readable by the web server, for example configuration files containing credentials, through a publicly accessible processed image.
Exploiting this vulnerability requires a way to upload files without a mime-type check, for example a public form of the Form Framework using a FileUpload or ImageUpload element without configured allowedMimeTypes (see TYPO3-CORE-SA-2026-032), which allows exploitation by unauthenticated visitors. Additionally, ImageMagick must be used for image processing, and its default system configuration must allow the MVG coder.
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-184Incomplete List of Disallowed Inputs CWE-434Unrestricted Upload of File with Dangerous Type
Show the promptExplain CVE-2026-125159 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125159?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125159?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125159 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
typo3:typo3 cms
Versions
From the CNA's record in the CVE List.
Product
Affected
TYPO3 CMS
from 14.0.0 before 14.3.12
TYPO3 CMS
from 13.0.0 before 13.4.40
TYPO3 CMS
from 12.0.0 before 12.4.52
TYPO3 CMS
from 11.0.0 before 11.5.57
TYPO3 CMS
from 10.0.0 before 10.4.63
Attack patterns (CAPEC)
CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
CAPEC-6 Argument Injection Likelihood: High · Severity: High
CAPEC-15 Command Delimiters Likelihood: High · Severity: High
CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
CAPEC-182 Flash Injection Likelihood: High · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.