# CVE-2026-104060: Worklenz SQL injection in reporting members endpoints

Source: https://junglewise.ai/threats/cve-2026-104060-worklenz-before-3-3-0-contains-an-sql-injection-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-104060 · Severity: medium · CVSS 6.5 · Published 2026-11-10

Worklenz is a project management and reporting platform. An authenticated attacker can inject SQL commands through the reporting members API endpoints to extract arbitrary database contents, including user password hashes, by exploiting unparameterized SQL queries. This allows data breach across all tenants in a shared instance.

Technologies: [Worklenz](https://junglewise.ai/threats/technologies/worklenz). Vendors: [Worklenz](https://junglewise.ai/threats/vendors/worklenz).

## 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)

## References

- [https://github.com/Worklenz/worklenz/commit/f58c7dbcc68fcda31a5cd4ce68d02af7ea8c37e1](https://github.com/Worklenz/worklenz/commit/f58c7dbcc68fcda31a5cd4ce68d02af7ea8c37e1)
- [https://github.com/Worklenz/worklenz/pull/624](https://github.com/Worklenz/worklenz/pull/624)

## Related threats

- [Worklenz task API authorization bypass](https://junglewise.ai/threats/cve-2026-85389-worklenz-task-api-authorization-bypass)
- [Worklenz SQL injection in sort-field pagination parameter](https://junglewise.ai/threats/cve-2026-85388-worklenz-sql-injection-in-sort-field-pagination-parameter)