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

GHSA-fp7q-xhhw-6rj3

HIGH

Path traversal vulnerability in the file manager

Also known asCVE-2023-29200
Published
Apr 26, 2023
Updated
Feb 16, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk52th percentile+0.22%
0.00%0.43%0.86%1.30%0.3%0.8%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

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

Impact

Authenticated users in the back end can list files outside the document root in the file manager.

Patches

Update to Contao 4.9.40, 4.13.21 or 5.1.4.

Workarounds

None.

References

https://contao.org/en/security-advisories/directory-traversal-in-the-file-manager

For more information

If you have any questions or comments about this advisory, open an issue in contao/contao.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistcontao/contao4.9.0&&< 4.9.404.9.40
🐘Packagistcontao/contao4.13.0&&< 4.13.214.13.21
🐘Packagistcontao/contao5.1.0&&< 5.1.45.1.4

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

Frequently Asked Questions

### Impact Authenticated users in the back end can list files outside the document root in the file manager. ### Patches Update to Contao 4.9.40, 4.13.21 or 5.1.4. ### Workarounds None. ### References https://contao.org/en/security-advisories/directory-traversal-in-the-file-manager ### For more information If you have any questions or comments about this advisory, open an issue in [contao/contao](https://github.com/contao/contao/issues/new/choose).
O3 Security · Impact-Aware SCA

Is GHSA-fp7q-xhhw-6rj3 in your dependencies?

O3 detects GHSA-fp7q-xhhw-6rj3 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-fp7q-xhhw-6rj3: Path traversal vulnerability in the file m… | O3 Security