Quick answers
- Is CVE-2026-104060 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104060 being exploited in the wild.
- How severe is CVE-2026-104060?
- Medium severity, with a CVSS score of 6.5, published 10 November 2026.
- Which products and versions are affected?
- Worklenz before 3.3.0.
- Is there a fix for CVE-2026-104060?
- Yes: fixed in 3.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104060 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104060?
- Check whether you run Worklenz 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.
How to fix
- Fixed in: 3.3.0
Technical details
SQL injection vulnerability in the reporting members endpoints (/api/v1/reporting/members/all and /api/v1/reporting/members/export) where the projects and status parameters are interpolated unparameterized into IN clauses in the getTeamMemberInsightData function. An authenticated attacker can exploit this using time-based blind SQL injection techniques to extract sensitive data across tenant boundaries. The vulnerability was fixed by converting to parameterized queries.
Affected products
- Worklenz Worklenz before 3.3.0
Timeline
- 2026-11-10: disclosed: Published to NVD
- 2026-10-21: patched: Security fix commit merged (f58c7db)