How severe is CVE-2019-11512?

CVE-2019-11512 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-11512?

CVE-2019-11512 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 CVE-2019-11512?

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

How do I detect CVE-2019-11512 in my Packagist dependencies?

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

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

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2019-11512 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-11512 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 CVE-2019-11512?

CVE-2019-11512 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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 CVE-2019-11512?

CVE-2019-11512 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 CVE-2019-11512 published, and has it been updated?

CVE-2019-11512 was published on July 9, 2019 and was last updated on October 24, 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

CRITICAL severity

CVE-2019-11512 — contao

CRITICALFix: contao/contao@87d92f8

CVE-2019-11512 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in contao/contao. A fix is available for contao/contao — see the affected versions and patch details below.

Contao SQL injection in the file manager

Also known asGHSA-vq59-x6mq-4wgw

Published

Jul 9, 2019

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% 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

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`composer require contao/contao:^4.4.39`
🐘Packagist	`contao/contao`	≥ 4.5.0&&< 4.7.5	4.7.5`composer require contao/contao:^4.7.5`
🐘Packagist	`contao/core-bundle`	≥ 4.1.0&&< 4.4.39	4.4.39`composer require contao/core-bundle:^4.4.39`
🐘Packagist	`contao/core-bundle`	≥ 4.5.0&&< 4.7.5	4.7.5`composer require contao/core-bundle:^4.7.5`

Affected Products

1 product · 2 configurations

Application

contaocontao

≥ 4.5.0 && < 4.7.5

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/contao, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update contao/contao to 4.4.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-11512 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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 CVE-2019-11512 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jul 9, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-11512

GHSA-vq59-x6mq-4wgw

References

Advisorycontao.org · security vulnerability cve 2019 11512 Advisorynvd.nist.gov · CVE 2019 11512 Webgithub.com · 87d92f823b08b91a0aeb522284537c8afcdb8aba Webgithub.com · CVE 2019 11512.yaml Webgithub.com · CVE 2019 11512.yaml

Related vulnerabilities

This CVE is critical severity — higher than any of the other 8 CVEs affecting contao/contao (highest there: high).

CVE-2026-57232CVE-2026-55824CVE-2026-55825CVE-2025-57756CVE-2025-57758CVE-2025-57759CVE-2025-57757CVE-2023-29200

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2019-11512 — contao

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2019-11512 in your dependencies?