Summary
Workarounds
Remove svg,svgz from the allowed upload file types in the system settings and from contao.editable_files in the config.yaml.
References
https://contao.org/en/security-advisories/cross-site-scripting-through-svg-uploads
For more information
If you have any questions or comments about this advisory, open an issue in contao/contao.
Impact
Users can upload SVG files with malicious code, which is then executed in the back end and/or front end.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Update to Contao 4.13.54, 5.3.30 or 5.5.6.
Frequently Asked Questions
- What is CVE-2025-29790? CVE-2025-29790 is a medium-severity cross-site scripting (XSS) vulnerability in contao/core-bundle (composer), affecting versions >= 4.0.0, < 4.13.54. It is fixed in 4.13.54, 5.3.30, 5.5.6. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which versions of contao/core-bundle are affected by CVE-2025-29790? contao/core-bundle (composer) versions >= 4.0.0, < 4.13.54 is affected.
- Is there a fix for CVE-2025-29790? Yes. CVE-2025-29790 is fixed in 4.13.54, 5.3.30, 5.5.6. Upgrade to this version or later.
- Is CVE-2025-29790 exploitable, and should I be worried? Whether CVE-2025-29790 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-29790 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-29790?
- Upgrade
contao/core-bundleto 4.13.54 or later - Upgrade
contao/core-bundleto 5.3.30 or later - Upgrade
contao/core-bundleto 5.5.6 or later
- Upgrade