CVE-2018-8947 is a high-severity (CVSS 7.5) CWE-312 vulnerability in rap2hpoutre/laravel-log-viewer. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for rap2hpoutre/laravel-log-viewer — see the affected versions and patch details below.
Plaintext Storage of Sensitive Information in Laravel Log Viewer before v0.13.0
EPSS Exploitation Probability
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
rap2hpoutre/laravel-log-viewerReal-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
rap2hpoutre Laravel Log Viewer before v0.13.0 relies on Base64 encoding for l, dl, and del requests, which makes it easier for remote attackers to bypass intended access restrictions, as demonstrated by reading arbitrary files via a dl request.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | rap2hpoutre/laravel-log-viewer | all versions | 0.13.0composer require rap2hpoutre/laravel-log-viewer:^0.13.0 |
Affected Products
laravel log viewerlaravel_log_viewer_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Laravel Log Viewer < 0.13.0 - Local File Download
by Haboob Team · Mar 26, 2018
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rap2hpoutre/laravel-log-viewer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rap2hpoutre/laravel-log-viewer to 0.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8947 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.
Frequently Asked Questions
Is CVE-2018-8947 in your dependencies?
Find it across Packagist, including transitive dependencies.