NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2018-20028 — contao

MEDIUMFix: contao/contao@bbe5fe1

CVE-2018-20028 is a medium-severity (CVSS 6.5) vulnerability in contao/contao. A fix is available for contao/contao — see the affected versions and patch details below.

Contao Information Disclosure via Access Control Flaws

Also known asGHSA-q99w-j4mj-7hj8
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk
0.00%0.47%0.95%1.42%0.3%0.9%May 26Sep 26Nov 26

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

3 pkgs affected
🐘contao/contao🐘contao/contao🐘contao/contao

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 3.x before 3.5.37, 4.4.x before 4.4.31 and 4.6.x before 4.6.11 has Incorrect Access Control.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcontao/contao≥ 3.0.0&&< 3.5.373.5.37composer require contao/contao:^3.5.37
🐘Packagistcontao/contao≥ 4.6.0&&< 4.6.114.6.11composer require contao/contao:^4.6.11
🐘Packagistcontao/contao≥ 4.4.0&&< 4.4.314.4.31composer require contao/contao:^4.4.31

Affected Products

1 product · 3 configurations
Application
contao cmscontao
≥ 4.6.0 && < 4.6.11
range

Detection & mitigation playbook

Open-source dependency

  1. 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.

  2. Fix

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

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Contao 3.x before 3.5.37, 4.4.x before 4.4.31 and 4.6.x before 4.6.11 has Incorrect Access Control.
O3 Security · Impact-Aware SCA

Is CVE-2018-20028 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-20028: contao — Fixed in 3.5.37