How severe is GHSA-v24p-7p4j-qvvf?

GHSA-v24p-7p4j-qvvf has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-v24p-7p4j-qvvf?

GHSA-v24p-7p4j-qvvf affects the following packages: contao/core-bundle (Packagist), contao/core-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-v24p-7p4j-qvvf?

Update contao/core-bundle to 4.13.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v24p-7p4j-qvvf is resolved across your whole dependency graph.

How do I detect GHSA-v24p-7p4j-qvvf in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/core-bundle, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-v24p-7p4j-qvvf if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-v24p-7p4j-qvvf actively exploited in the wild?

No public exploit code has been indexed for GHSA-v24p-7p4j-qvvf 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 is the EPSS score for GHSA-v24p-7p4j-qvvf?

GHSA-v24p-7p4j-qvvf has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-v24p-7p4j-qvvf?

GHSA-v24p-7p4j-qvvf 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 GHSA-v24p-7p4j-qvvf published, and has it been updated?

GHSA-v24p-7p4j-qvvf was published on April 9, 2024 and was last updated on September 10, 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

Not in CISA KEV

MEDIUM severity

Contao: Cross site scripting in the file managerGHSA-v24p-7p4j-qvvf

MEDIUMFix: contao/contao@878d28d

GHSA-v24p-7p4j-qvvf is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in contao/core-bundle. A fix is available for contao/core-bundle — see the affected versions and patch details below.

Also known asCVE-2024-28190

Published

Apr 9, 2024

Updated

Sep 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-v24p-7p4j-qvvf.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐘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

Impact

Users can insert malicious code into file names when uploading files, which is then executed in tooltips and popups in the backend.

Patches

Update to Contao 4.13.40 or Contao 5.3.4.

Workarounds

Disable uploads for untrusted users.

References

https://contao.org/en/security-advisories/cross-site-scripting-in-the-file-manager

For more information

If you have any questions or comments about this advisory, open an issue in contao/contao.

Credits

Thanks to Alexander Wuttke for reporting this vulnerability.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/core-bundle`	≥ 4.0.0&&< 4.13.40	4.13.40`composer require contao/core-bundle:^4.13.40`
🐘Packagist	`contao/core-bundle`	≥ 5.0.0-RC1&&< 5.3.4	5.3.4`composer require contao/core-bundle:^5.3.4`

Affected Products

1 product · 2 configurations

Application

contaocontao

≥ 5.0.0 && < 5.3.4

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update contao/core-bundle to 4.13.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v24p-7p4j-qvvf is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Users can insert malicious code into file names when uploading files, which is then executed in tooltips and popups in the backend. ### Patches Update to Contao 4.13.40 or Contao 5.3.4. ### Workarounds Disable uploads for untrusted users. ### References https://contao.org/en/security-advisories/cross-site-scripting-in-the-file-manager ### For more information If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose). ### Credits Thanks to Alexander Wuttke for reporting this vulnerability