Leantime's Users::getUser method in the JSON-RPC API lacks proper authorization checks, allowing authenticated users to retrieve full user credential rows including password hashes, TOTP secrets, and session tokens. Attackers can exploit this by calling users.getUser with arbitrary user IDs to enumerate all accounts and obtain credentials for offline password cracking, 2FA bypass, and session hijacking.
CVE-2026-59712
This high-severity CVE scores 8.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(low)
- EPSS
- —
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 6, 2026
Advisory Details (4)
Auto-updated Jul 6, 2026Leantime - Credential Disclosure via Unauthenticated JSON-RPC users.getUser Method | Advisories | VulnCheck
https://www.vulncheck.com/advisories/leantime-credential-disclosure-via-unauthenticated-json-rpc-users-getuser-methodauthenticated full-row credential dump via JSON-RPC users.getUser (password/2FA/session) · Issue #3556 · Leantime/leantime · GitHub
https://github.com/Leantime/leantime/issues/3556commit 4f2612d13e0e (Leantime/leantime)
Fix landed in Leantime/leantime commit 4f2612d13e0e — awaiting tagged release
https://github.com/Leantime/leantime/commit/4f2612d13e0e8a2093092a846b44506cf133b671GitHub - Leantime/leantime: Leantime is a goals focused project management system for non-project managers. Building with ADHD, Autism, and dyslexia in mind. · GitHub
https://github.com/Leantime/leantimeVendor Advisories for CVE-2026-59712(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 21:05 UTCEG score recompute
- 2026-07-06 21:04 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-59712?
When was CVE-2026-59712 disclosed?
What is the CVSS score of CVE-2026-59712?
How do I remediate CVE-2026-59712?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59712
Is Your Infrastructure Affected by CVE-2026-59712?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.