Is rap2hpoutre/laravel-log-viewer 0.7 vulnerable?

Composer · 2 releases from 0.7.0 to 0.7.1 · latest rap2hpoutre/laravel-log-viewer is 3.1.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. rap2hpoutre/laravel-log-viewer 0.7.1, the last 0.7 release, is affected by 1 known security advisory (1 high), including CVE-2018-8947. Upgrade to 0.13.0 or later to fix all of them.

Upgrade with:composer require rap2hpoutre/laravel-log-viewer:^0.13.0

Is your project on an affected rap2hpoutre/laravel-log-viewer?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting rap2hpoutre/laravel-log-viewer 0.7.1

  • HighCVE-2018-8947GHSA-63qj-p8gh-5xxx13 May 2022

    Plaintext Storage of Sensitive Information in Laravel Log Viewer before v0.13.0

    Affected
    <0.13.0
    Fixed in
    0.13.0

Every rap2hpoutre/laravel-log-viewer 0.7.x release

Affected: 0.7.0 to 0.7.1. Latest rap2hpoutre/laravel-log-viewer: 3.1.0.

VersionKnown advisories
rap2hpoutre/laravel-log-viewer 0.7.1CVE-2018-8947
rap2hpoutre/laravel-log-viewer 0.7.0CVE-2018-8947

Which of your client projects are still on rap2hpoutre/laravel-log-viewer 0.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact rap2hpoutre/laravel-log-viewer version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other rap2hpoutre/laravel-log-viewer versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.