Quick answers
- Is CVE-2026-73847 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73847 being exploited in the wild.
- How severe is CVE-2026-73847?
- Medium severity, with a CVSS score of 6.8, published 14 August 2026.
- Which products and versions are affected?
- Emlog 2.6.23 and earlier.
- Is there a fix for CVE-2026-73847?
- 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-73847 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-73847?
- 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
This is a CSRF vulnerability combined with multiple authentication and authorization flaws in the AI Assistant's execute_tool endpoint (admin/ai.php). The vulnerability exploits the absence of CSRF token validation (no LoginAuth::checkToken() call), a missing SameSite attribute on the authentication cookie (enabling Chrome's Lax+POST grace period), and a hardcoded public confirmation string ("confirm") instead of a secret token. Read operations execute with no confirmation requirement, while write operations are protected only by the public string. The password redaction mechanism can be bypassed by aliasing password columns (e.g., SELECT password AS pwd_hash). An attacker delivers a forged cross-site request to a recently logged-in administrator, gaining full database read access (including password hashes) and write access to all tables except blog, enabling direct user table modification for account takeover. No patched version is available as of the advisory date.
Affected products
- Emlog Emlog 2.6.23 and earlier
Timeline
- 2026-08-14: disclosed: CVE-2026-73847 and GHSA-v6wr-4x55-7qp5 published