Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-vcgg-hp4r-87gx

CRITICAL

Contao Does Not Invalidate Existing Sessions When Password Changes

Also known asCVE-2019-10641
Published
May 14, 2022
Updated
Apr 25, 2024
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk60th percentile+0.78%
0.00%0.52%1.03%1.55%0.3%1.0%Dec 25Apr 26Jun 26

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

5 pkgs affected
🐘contao/contao🐘contao/contao🐘contao/core-bundle🐘contao/core-bundle🐘contao/core

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

Security researcher Ali Razzaq has discovered that existing sessions are not correctly invalidated when a user changes their password in the backend or frontend.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcontao/contao4.0.0&&< 4.4.374.4.37
🐘Packagistcontao/contao4.5.0&&< 4.7.34.7.3
🐘Packagistcontao/core-bundle4.0.0&&< 4.4.374.4.37
🐘Packagistcontao/core-bundle4.5.0&&< 4.7.34.7.3
🐘Packagistcontao/core3.0.0&&< 3.5.393.5.39

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

  2. Fix

    Update contao/contao to 4.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vcgg-hp4r-87gx is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-vcgg-hp4r-87gx 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-vcgg-hp4r-87gx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Security researcher Ali Razzaq has discovered that existing sessions are not correctly invalidated when a user changes their password in the backend or frontend.
O3 Security · Impact-Aware SCA

Is GHSA-vcgg-hp4r-87gx in your dependencies?

O3 detects GHSA-vcgg-hp4r-87gx across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.