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
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. the CNA's CVSS baseline 8.1; sources differ by 0.0.
- 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(high)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 16.5%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 20, 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 13× in last 7d / 52× 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-24 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:21 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 03:36 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 15:17 UTCGHSA enrichment
- 2026-07-16 02:57 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 14:38 UTCGHSA enrichment
- 2026-07-15 02:18 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 13:59 UTCGHSA enrichment
- 2026-07-14 01:39 UTCGHSA enrichment
Show 27 moreShow fewer
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 13:20 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 01:00 UTCGHSA enrichment
- 2026-07-12 12:41 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 00:22 UTCGHSA enrichment
- 2026-07-11 12:02 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 23:42 UTCGHSA enrichment
- 2026-07-10 11:22 UTCGHSA enrichment
- 2026-07-09 23:03 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 10:43 UTCGHSA enrichment
- 2026-07-08 22:23 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 10:03 UTCGHSA enrichment
- 2026-07-07 21:44 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 09:25 UTCGHSA enrichment
- 2026-07-06 21:05 UTCEG score recompute
- 2026-07-06 21:04 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(5)
What is CVE-2026-59712?
When was CVE-2026-59712 disclosed?
Is CVE-2026-59712 actively exploited?
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.