Quick answers
- Is CVE-2026-34787 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34787 being exploited in the wild.
- How severe is CVE-2026-34787?
- Medium severity, with a CVSS score of 6.5, published 3 April 2026.
- Which products and versions are affected?
- Emlog <= 2.6.2.
- Is there a fix for CVE-2026-34787?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-34787 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34787?
- Check whether you run Emlog at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Local File Inclusion (LFI) vulnerability exists in Emlog versions 2.6.2 and prior within the 'admin/plugin.php' component. The '$plugin' parameter, retrieved via a GET request, is passed directly into a 'require_once' statement at line 80 without sufficient sanitization or path validation. While the application uses 'addslashes()', it fails to prevent path traversal sequences (../), allowing an authenticated administrator to include arbitrary PHP files from the server's filesystem. This can result in information disclosure or remote code execution if an attacker can influence the contents of a file on the disk. As of the advisory date, no official patch is available; developers recommend using 'basename()' and a whitelist to validate plugin names.
Affected products
- Emlog Emlog <= 2.6.2
Timeline
- 2026-03-31: advisory: GitHub Security Advisory published
- 2026-04-03: disclosed: CVE published to NVD