How severe is GHSA-vq59-x6mq-4wgw?

GHSA-vq59-x6mq-4wgw has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-vq59-x6mq-4wgw?

GHSA-vq59-x6mq-4wgw affects the following packages: contao/contao (Packagist), contao/contao (Packagist), contao/core-bundle (Packagist), contao/core-bundle (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vq59-x6mq-4wgw?

Update contao/contao to 4.4.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vq59-x6mq-4wgw is resolved across your whole dependency graph.

How do I detect GHSA-vq59-x6mq-4wgw in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/contao. 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 GHSA-vq59-x6mq-4wgw 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 GHSA-vq59-x6mq-4wgw?

O3 pinpoints whether GHSA-vq59-x6mq-4wgw 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 GHSA-vq59-x6mq-4wgw actively exploited in the wild?

No public exploit code has been indexed for GHSA-vq59-x6mq-4wgw 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-vq59-x6mq-4wgw?

GHSA-vq59-x6mq-4wgw has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 70th 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-vq59-x6mq-4wgw?

GHSA-vq59-x6mq-4wgw is classified as SQL Injection (CWE-89). 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-vq59-x6mq-4wgw published, and has it been updated?

GHSA-vq59-x6mq-4wgw was published on May 24, 2022 and was last updated on April 25, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-vq59-x6mq-4wgw: Contao SQL injection in the file manager…

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk70th percentile+1.16%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐘contao/contao🐘contao/contao🐘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

David Wind, penetration tester with A1 Digital, has discovered that the SQL injection vulnerability originally published under CVE-2017-16558 can still be exploited in the file manager in Contao 4.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/contao`	≥ 4.1.0&&< 4.4.39	4.4.39
🐘Packagist	`contao/contao`	≥ 4.5.0&&< 4.7.5	4.7.5
🐘Packagist	`contao/core-bundle`	≥ 4.1.0&&< 4.4.39	4.4.39
🐘Packagist	`contao/core-bundle`	≥ 4.5.0&&< 4.7.5	4.7.5

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for contao/contao. 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/contao to 4.4.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vq59-x6mq-4wgw 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 GHSA-vq59-x6mq-4wgw 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 GHSA-vq59-x6mq-4wgw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

David Wind, penetration tester with A1 Digital, has discovered that the SQL injection vulnerability originally published under CVE-2017-16558 can still be exploited in the file manager in Contao 4.

O3 Security · Impact-Aware SCA

Is GHSA-vq59-x6mq-4wgw in your dependencies?

O3 detects GHSA-vq59-x6mq-4wgw 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

GHSA-vq59-x6mq-4wgw