Quick answers
- Is CVE-2026-53758 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53758 being exploited in the wild.
- How severe is CVE-2026-53758?
- Informational severity, published 4 September 2026.
- Which products and versions are affected?
- Emlog 2.6.29 and prior.
- Is there a fix for CVE-2026-53758?
- 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-53758 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-53758?
- 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
Emlog processes article Markdown using the Parsedown library without enabling safe mode (setSafeMode(true) is not called), allowing raw HTML including <script> and <img onerror> tags to pass through unescaped. The vulnerability is a stored XSS flaw in the article rendering logic (include/lib/function.base.php) where attacker-supplied HTML is persisted and rendered to all site visitors without additional sanitization. The attack requires author or admin privileges to create or edit an article, but impact extends to all visitors including unauthenticated users and administrators. An attacker can steal session cookies, perform unauthorized actions, or deliver malware. At publication, no patches are available.
Affected products
- Emlog Emlog 2.6.29 and prior
Timeline
- 2026-06-10: disclosed
- 2026-09-04: advisory