Possibility for Denial of Service by overwriting PHP files with language exportsGHSA-3fvf-2gp4-89wq
GHSA-3fvf-2gp4-89wq is a security vulnerability in barryvdh/laravel-translation-manager. A fix is available for barryvdh/laravel-translation-manager — see the affected versions and patch details below.
Real-World Exposure
barryvdh/laravel-translation-managerReal-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
Laravel Translation Manager didn't check the locale name, which allowed directory traversal when exporting files. The content would be a PHP file returning an array of translations, but this could lead to unexpected results, like denial of service. Access to the Laravel Translation Manager is required, because a new locale would have to be added and published.
Patches
Version 0.6.2 fixes this issue.
Workarounds
Only allow trusted admins to publish/edit translations.
References
https://github.com/barryvdh/laravel-translation-manager/pull/417
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/barryvdh/laravel-translation-manager
- Email me (see Github profile)
Credits
Found and reported by Natalia Trojanowska
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | barryvdh/laravel-translation-manager | all versions | 0.6.2composer require barryvdh/laravel-translation-manager:^0.6.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for barryvdh/laravel-translation-manager, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update barryvdh/laravel-translation-manager to 0.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3fvf-2gp4-89wq is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-3fvf-2gp4-89wq in your dependencies?
Find it across Packagist, including transitive dependencies.