Quick answers
- Is CVE-2026-50869 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50869 being exploited in the wild.
- How severe is CVE-2026-50869?
- Informational severity, with a CVSS score of 7.2, published 15 June 2026.
- Which products and versions are affected?
- Bludit 3.19.0.
- Is there a fix for CVE-2026-50869?
- 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-50869 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-50869?
- Check whether you run Bludit 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 directory traversal vulnerability exists in the `uploadFile()` function within `bl-plugins/api/plugin.php` of Bludit v3.19.0. The application fails to sanitize the `filename` parameter from multipart form data, directly appending it to the upload path. An authenticated attacker with administrator privileges can provide a crafted filename containing path traversal sequences (e.g., `../../../../.htaccess`). While the application blocks some script extensions, it does not normalize path segments, enabling the placement of configuration files like `.htaccess` or `.user.ini` in sensitive directories. This can lead to arbitrary PHP code execution or filesystem integrity loss depending on the server configuration.
Affected products
- Bludit Bludit 3.19.0
Timeline
- 2026-06-13: disclosed: Initial discovery and Gist publication
- 2026-06-15: advisory: CVE-2026-50869 published by NVD/MITRE