Leantime up to 3.6.2 TwoFA Service userId improper authorization

Summaryinfo

A vulnerability identified as critical has been detected in Leantime up to 3.6.2. Affected by this issue is the function leantime.rpc.TwoFA.TwoFA.getSetupData/leantime.rpc.TwoFA.TwoFA.saveSecret/leantime.rpc.TwoFA.TwoFA.verifyAndEnable/leantime.rpc.TwoFA.TwoFA.disable2FA of the component TwoFA Service. This manipulation of the argument userId causes improper authorization. This vulnerability is handled as CVE-2026-54418. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical was found in Leantime up to 3.6.2. Affected by this vulnerability is the function leantime.rpc.TwoFA.TwoFA.getSetupData/leantime.rpc.TwoFA.TwoFA.saveSecret/leantime.rpc.TwoFA.TwoFA.verifyAndEnable/leantime.rpc.TwoFA.TwoFA.disable2FA of the component TwoFA Service. The manipulation of the argument userId with an unknown input leads to a improper authorization vulnerability. The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Leantime through 3.6.2 exposes the JSON-RPC methods leantime.rpc.TwoFA.TwoFA.getSetupData, saveSecret, verifyAndEnable, and disable2FA, which act on a caller-supplied userId parameter with no ownership check, session pinning, or permission-attribute gate (unlike other RPC-exposed methods in the same dispatcher). Any authenticated user can invoke getSetupData with an arbitrary userId to read that user's live TOTP secret, or disable2FA to strip another account's two-factor authentication entirely, fully defeating account-level 2FA protection. This is related to CVE-2026-15509, which covers a similar missing-authorization pattern in the JSON-RPC editUser/addUser role-assignment path in the same application; the TwoFA service methods addressed here are a distinct, independently fixable set of RPC endpoints.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-54418 since 06/13/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/05/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Leantime

Version

• 3.6.0
• 3.6.1
• 3.6.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion