Quick answers
- Is CVE-2026-42287 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42287 being exploited in the wild.
- How severe is CVE-2026-42287?
- Informational severity, with a CVSS score of 10, published 8 May 2026.
- Which products and versions are affected?
- Emlog Pro < 2.6.11.
- Is there a fix for CVE-2026-42287?
- 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-42287 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-42287?
- Check whether you run Emlog Pro 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 SQL injection vulnerability exists in Emlog's `log_model.php` within the `addLog()` and `updateLog()` functions. The root cause is the direct concatenation of user-supplied input from article fields (such as title and content) into SQL INSERT and UPDATE queries without proper sanitization or escaping. An unauthenticated or low-privileged attacker can exploit this via the `/admin/article_save.php` endpoint by submitting specially crafted JSON payloads. Successful exploitation allows for arbitrary SQL execution, which can be used to bypass authentication, escalate privileges to administrator, or drop database tables. The issue is resolved in version 2.6.11 by implementing `escape_string()` on all user-controlled inputs.
Affected products
- Emlog Emlog < 2.6.11
Timeline
- 2026-04-22: advisory: GitHub Security Advisory published
- 2026-05-08: disclosed: CVE published to NVD