How severe is GHSA-q99w-j4mj-7hj8?

GHSA-q99w-j4mj-7hj8 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-q99w-j4mj-7hj8?

GHSA-q99w-j4mj-7hj8 affects the following packages: contao/contao (Packagist), contao/contao (Packagist), contao/contao (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-q99w-j4mj-7hj8?

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

How do I detect GHSA-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8?

O3 pinpoints whether GHSA-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8?

GHSA-q99w-j4mj-7hj8 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 56th 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.

When was GHSA-q99w-j4mj-7hj8 published, and has it been updated?

GHSA-q99w-j4mj-7hj8 was published on May 13, 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-q99w-j4mj-7hj8: Contao Information Disclosure via Access C…

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk56th percentile+0.65%

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

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

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`contao/contao`	≥ 3.0.0&&< 3.5.37	3.5.37
🐘Packagist	`contao/contao`	≥ 4.6.0&&< 4.6.11	4.6.11
🐘Packagist	`contao/contao`	≥ 4.4.0&&< 4.4.31	4.4.31

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 3.5.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-q99w-j4mj-7hj8 in your dependencies?

O3 detects GHSA-q99w-j4mj-7hj8 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-q99w-j4mj-7hj8