Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113358 Overview
CVE-2026-113358 is a missing authentication vulnerability [CWE-306] affecting LavaLite CMS through version 10.1.2. The flaw resides in the Filer module, specifically the filer/download and filer/display routes handled by FileController. Unauthenticated attackers can send requests to these endpoints and supply arbitrary disk names and paths. The controller then retrieves and returns the referenced files without verifying the caller's identity or authorization. Attackers can download private uploads from local storage or from configured remote Amazon S3 disks. Any sensitive content stored through the Filer module, including customer uploads, internal documents, and backups, is reachable over the network.
Critical Impact
Remote unauthenticated attackers can download arbitrary files from local or S3-backed storage disks configured in LavaLite CMS.
Affected Products
- LavaLite CMS versions through 10.1.2
- Litepie Framework Filer module (FileController)
- Deployments using local or remote S3 storage disks exposed through the Filer routes
Discovery Timeline
- 2026-10-20 - CVE CVE-2026-113358 published to NVD
- 2026-10-20 - Last updated in NVD database
Technical Details for CVE-2026-113358
Vulnerability Analysis
The Filer module in LavaLite CMS exposes two routes, filer/download and filer/display, that are routed to FileController without authentication middleware. The controller accepts a disk name and a file path from request parameters and passes them to Laravel's storage abstraction. Because no identity check or ownership validation is performed, any unauthenticated client can request private assets through the public web interface. Attackers can target the default local disk to read files uploaded by other users or point requests at a configured s3 disk to pull objects from the backing bucket. The outcome is confidentiality loss across every disk reachable from the application configuration.
Root Cause
The root cause is missing authentication and authorization on sensitive file-serving routes. The Filer/routes/web.php definitions register the download and display endpoints on the public route group rather than behind an auth middleware. FileController additionally trusts the client-supplied disk and path parameters without verifying that the current session owns or is permitted to read the referenced resource.
Attack Vector
The attack vector is network-based and requires no privileges or user interaction. An attacker issues an HTTP GET request to /filer/download or /filer/display, supplying a disk identifier such as local or s3 along with a file path. The server resolves the request through FileController and streams the file back in the response. See the VulnCheck Advisory on LavaLite, the GitHub FileController Source Code, and the GitHub Gist PoC Code for technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-113358
Indicators of Compromise
- Unauthenticated HTTP requests to /filer/download or /filer/display paths in web access logs.
- Requests containing disk parameters such as local, public, or s3 combined with file paths pointing at private resources.
- Anomalous S3 object GetObject calls originating from the LavaLite application role, especially for files not referenced by legitimate user workflows.
Detection Strategies
- Inspect reverse-proxy and web server logs for high-volume or sequential enumeration of filenames against the Filer endpoints.
- Correlate application logs with cloud storage audit trails (for example AWS CloudTrail S3 Data Events) to identify object reads not tied to authenticated user sessions.
- Alert on requests to Filer routes that lack a valid session cookie or authentication header.
Monitoring Recommendations
- Enable verbose request logging on the LavaLite application tier and ship logs to a central analytics pipeline.
- Monitor outbound S3 egress volume from the application host for sudden spikes consistent with bulk file retrieval.
- Track 200-status responses on filer/download and filer/display broken down by source IP to detect scraping behavior.
How to Mitigate CVE-2026-113358
Immediate Actions Required
- Block public access to /filer/download and /filer/display at the reverse proxy or web application firewall until a patched version is deployed.
- Rotate credentials and access keys for any S3 buckets configured as Filer disks that may have been exposed.
- Audit storage disks for sensitive content and remove or relocate files that must not be served through the web tier.
Patch Information
At the time of publication, no fixed version is referenced in the advisory data; LavaLite CMS releases up to and including v10.1.2 are vulnerable. Monitor the LavaLite repository for a security release that adds authentication middleware and disk allow-listing to the Filer routes, and consult the VulnCheck Advisory on LavaLite for update guidance.
Workarounds
- Add authentication middleware to the Filer routes in web.php so that only authenticated sessions can invoke FileController actions.
- Restrict the disks referenced by FileController to a controlled allow-list and reject client-supplied disk identifiers such as s3.
- Serve private user uploads through signed, time-limited URLs generated server-side rather than through the vulnerable public routes.
# Example reverse-proxy block (nginx) to deny public access to Filer routes
location ~ ^/filer/(download|display) {
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

