LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8947: rap2hpoutre Laravel Log Viewer before v0.13.0 relies on Base64 encoding for l, dl, and del requests, which...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-8947 affects rap2hpoutre Laravel Log Viewer before v0.13.0. The component treated Base64-encoded request values as a meaningful barrier, making it easier for remote attackers to bypass intended restrictions and read arbitrary files. For businesses, the risk is exposure of server files, logs, credentials, or application secrets where the log viewer is deployed and reachable.

Executive priority

Prioritize remediation for any internet-facing or weakly protected deployment. The issue can expose arbitrary server files, and public exploit information exists, but the provided sources do not prove active exploitation or quantify prevalence.

Technical view

The flaw is an access-restriction bypass in Laravel Log Viewer request handling for l, dl, and del parameters. The CVE description states Base64 encoding was relied on for these requests, with arbitrary file reading demonstrated through a dl request. Upstream references identify v0.13.0 and a related commit as the remediation point.

Likely exposure

Exposure is limited to environments running rap2hpoutre Laravel Log Viewer before v0.13.0, especially if its routes are reachable by untrusted users. The source bundle does not provide CPEs, package manifests, CVSS, or default deployment details.

Exploitation context

The CVE is not listed as KEV in the provided bundle, so active exploitation is not established. A public Exploit-DB reference exists, indicating public exploit information has been available, but this assessment does not rely on or reproduce offensive details.

Researcher notes

The evidence is concise: CVE text identifies the weakness, affected version range, and arbitrary file read demonstration. The bundle lacks CVSS, CWE, CPEs, and detailed vendor advisory text, so validation should focus on package version, route exposure, and upstream v0.13.0 changes.

Mitigation direction

  • Upgrade rap2hpoutre Laravel Log Viewer to v0.13.0 or later.
  • Restrict log viewer routes to trusted administrators only.
  • Remove the package from production if operationally unnecessary.
  • Review upstream release and commit notes before deployment.
  • Check exposed logs and secrets if the component was internet-accessible.

Validation and detection

  • Inventory Laravel applications for rap2hpoutre Laravel Log Viewer usage.
  • Confirm installed versions are v0.13.0 or later.
  • Verify log viewer routes require authentication and authorization.
  • Review access logs for unusual file download activity.
  • Confirm no sensitive files or secrets were exposed through logs.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-8947 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.