How severe is CVE-2025-29790?

No CVSS score has been assigned to CVE-2025-29790 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-29790?

CVE-2025-29790 affects the following packages: contao/core-bundle (Packagist), contao/core-bundle (Packagist), contao/core-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-29790?

Update contao/core-bundle to 4.13.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-29790 is resolved across your whole dependency graph.

How do I detect CVE-2025-29790 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core-bundle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-29790 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-29790?

O3 pinpoints whether CVE-2025-29790 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-29790 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-29790 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2025-29790?

CVE-2025-29790 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-29790 published, and has it been updated?

CVE-2025-29790 was published on March 18, 2025 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2025-29790

CVE-2025-29790 is a Cross-site Scripting (XSS) vulnerability in contao/core-bundle. O3 Security confirms whether CVE-2025-29790 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Contao allows cross-site scripting through SVG uploads

Also known asGHSA-vqqr-fgmh-f626

Published

Mar 18, 2025

Updated

Aug 7, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

🐘contao/core-bundle🐘contao/core-bundle🐘contao/core-bundle

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Contao is an Open Source CMS. Users can upload SVG files with malicious code, which is then executed in the back end and/or front end. This vulnerability is fixed in Contao 4.13.54, 5.3.30, or 5.5.6.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core-bundle`	≥ 4.0.0&&< 4.13.54	4.13.54
🐘Packagist	`contao/core-bundle`	≥ 5.3.0&&< 5.3.30	5.3.30
🐘Packagist	`contao/core-bundle`	≥ 5.4.0&&< 5.5.6	5.5.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core-bundle. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update contao/core-bundle to 4.13.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-29790 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-29790 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-29790. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Contao is an Open Source CMS. Users can upload SVG files with malicious code, which is then executed in the back end and/or front end. This vulnerability is fixed in Contao 4.13.54, 5.3.30, or 5.5.6.

O3 Security · Impact-Aware SCA

Is CVE-2025-29790 in your dependencies?

O3 detects CVE-2025-29790 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works