Authenticated local file inclusion via page_slug traversal
Published Feb 5, 2020 · Updated Aug 4, 2024
Local file inclusion in Lotus Core CMS 1.0.1 allows remote authenticated users to include PHP files via the page_slug parameter. index.php appends .php to page_slug, checks the resulting path with file_exists(), and includes it without sanitizing traversal sequences. A valid session is required; a crafted relative path with a null byte can select an existing local file for server-side inclusion.
Summary
What happened
Local file inclusion in Lotus Core CMS 1.0.1 allows remote authenticated users to include PHP files via the page_slug parameter. index.php appends .php to page_slug, checks the resulting path with file_exists(), and includes it without sanitizing traversal sequences. A valid session is required; a crafted relative path with a null byte can select an existing local file for server-side inclusion.
The record
- CVE
- CVE-2020-8641
- Published
- Feb 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Lotus Core CMS 1.0.1 - Local File Inclusionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo