Web Application
CVE-2026-54418 high CVSS 8.1

Leantime through 3.6.2 exposes the JSON-RPC methods leantime.rpc.TwoFA.TwoFA.getSetupData,...

Summary

Leantime through 3.6.2 exposes the JSON-RPC methods leantime.rpc.TwoFA.TwoFA.getSetupData,...

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

AI summary

Written by an external AI model and may contain mistakes. Check the original description and references below before acting on it.

Leantimeのバージョン3.6.2までのシステムでは、所有者確認なしに任意のユーザーIDを指定してJSON-RPCメソッドが操作できます。これにより、任意のユーザーの2要素認証を解除したり、TOTP秘密を読み取ることができます。この欠陥により、2FA保護が無効となる可能性があります。

❓ What is the problem

所有者確認なしにJSON-RPCメソッドの操作が可能な脆弱性。

📍 Affected scope

Leantime 3.6.2までのバージョン。

🔥 Severity

任意のユーザーの2FAを無効化できるため、アカウント保護が完全に無効化される。

🔧 How to fix

JSON-RPCメソッドに所有者確認と権限属性ゲートを追加する。

🛡️ Workaround

現時点では情報なし。

🔍 Detection

認証ユーザーが無効な2FA操作を行った痕跡をログで確認する。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details