Quick answers
- Is CVE-2026-15509 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-15509 being exploited in the wild.
- How severe is CVE-2026-15509?
- Medium severity, with a CVSS score of 6.3, published 12 July 2026.
- Which products and versions are affected?
- Leantime up to 3.8.0.
- Is there a fix for CVE-2026-15509?
- 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-15509 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-15509?
- Check whether you run Leantime 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 broken access control vulnerability (CWE-862) exists in the JSON-RPC endpoint of Leantime versions up to 3.8.0. The 'editUser' and 'addUser' methods in the Users service fail to implement authorization checks, relying on the dispatcher which only verifies if a method is tagged with '@api'. An authenticated attacker with low privileges (e.g., Editor, Read-only) can invoke these methods to modify their own 'role' parameter to 'Owner' (role ID 50) or create new administrative accounts. This flaw can be further leveraged to achieve Remote Code Execution (RCE) by installing malicious plugins, a capability reserved for Owner accounts. The vendor has not yet released a patch.
Affected products
- Leantime Leantime up to 3.8.0
Timeline
- 2026-06-02: disclosed: Vulnerability reported to vendor and VulDB by Bytium.
- 2026-07-12: advisory: Public disclosure via NVD and VulDB.