CVE-2018-8947 in the critical feed json
Plaintext Storage of Sensitive Information in Laravel Log Viewer before v0.13.0
published 2018-03-25 8 y ago modified 2026-06-17 4 mo ago also GHSA-63qj-p8gh-5xxx , EUVD-2022-2704
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.0%
- EPSS 11.0% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
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.
Patch / fix
- packagist rap2hpoutre/laravel-log-viewer 0.13.0
- laravel_log_viewer_project laravel_log_viewer 0.13.0
Timeline
- Published
- First public exploit (EDB-44343)
Exploit prediction
11.02% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44343 Laravel Log Viewer < 0.13.0 - Local File Download webapps, 2018-03-26
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | rap2hpoutre/laravel-log-viewer | <0.13.0 |
0.13.0 |
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
-
github.com
/rap2hpoutre/laravel-log-viewer/commit/cda89c06dc5331d06fab863d7cb1c4047ad68357
web, patch, third-party-advisory
-
exploit-db.com
/exploits/44343/
exploit, third-party-advisory, vdb-entry
-
github.com
/rap2hpoutre/laravel-log-viewer/releases/tag/v0.13.0
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-8947
advisory
-
exploit-db.com
/exploits/44343
web
Sources
- CVE List CVE-2018-8947
- GitHub Advisory GHSA-63qj-p8gh-5xxx
- NVD CVE-2018-8947
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.