Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85990 Overview
Leantime, an open source project management system, contains a privilege escalation vulnerability in its JSON-RPC dispatcher prior to version 3.10.0. The flaw resides in app/Domain/Api/Controllers/Jsonrpc.php, where PermissionEnforcer::enforce allows methods lacking a RequiresPermission attribute to execute. A low-privilege authenticated user can invoke leantime.rpc.api.api.createApiKeyWithProjects and create an interactive administrator account with an attacker-chosen role. The same missing per-method authorization exposes plugin management methods including Plugins::installPlugin, Plugins::enablePlugin, Plugins::disablePlugin, and Plugins::removePlugin to any authenticated user. The issue is tracked under [CWE-269] Improper Privilege Management.
Critical Impact
Any authenticated low-privilege user can escalate to administrator and install, enable, disable, or remove plugins without authorization.
Affected Products
- Leantime versions prior to 3.10.0
- Leantime JSON-RPC API surface (app/Domain/Api/Controllers/Jsonrpc.php)
- Leantime Plugins management service
Discovery Timeline
- 2026-10-13 - CVE-2026-85990 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-85990
Vulnerability Analysis
The vulnerability stems from Leantime's JSON-RPC dispatcher exposing public API service methods without per-method authorization checks. The PermissionEnforcer::enforce routine permits any method that lacks an explicit RequiresPermission attribute. This default-allow behavior turns the JSON-RPC surface into an unguarded administrative channel for provisionally grouped account-creation and plugin-management methods.
An authenticated attacker with an ordinary browser session can send a JSON-RPC request including the X-Requested-With: XMLHttpRequest header. The request targets leantime.rpc.api.api.createApiKeyWithProjects, which reaches Api::createApiKeyWithProjects and accepts an attacker-controlled role parameter. The method creates an interactive administrator account, bypassing the role separation that Leantime otherwise enforces through its permission system.
The same missing authorization layer exposes plugin lifecycle operations. Low-privilege users can install arbitrary plugins, enabling code paths that extend the application and provide additional execution surfaces inside the Leantime instance.
Root Cause
The root cause is improper privilege management [CWE-269]. The PermissionEnforcer treats absence of a RequiresPermission attribute as implicit authorization rather than denying by default. Service methods such as createApiKeyWithProjects and the Plugins installer methods were never annotated, which left them reachable through the JSON-RPC entry point once a user authenticated.
Attack Vector
The attack vector is network-based and requires only low-privilege authentication. The attacker issues a JSON-RPC call carrying the standard X-Requested-With: XMLHttpRequest header and the target method identifier. No user interaction from an administrator is required.
// Security patch excerpt - app/Domain/Api/Services/Api.php
use Leantime\Domain\Api\Repositories\Api as ApiRepository;
use Leantime\Domain\Auth\Services\UserSessionBuilder;
use Leantime\Domain\Menu\Repositories\Menu as MenuRepository;
+use Leantime\Domain\Projects\Permissions\ProjectsPermissions;
use Leantime\Domain\Projects\Repositories\Projects as ProjectRepository;
use Leantime\Domain\Users\Repositories\Users as UserRepository;
use RangeException;
Source: GitHub Commit 5605e5e
// Onboarding service hardening - app/Domain/Auth/Services/Onboarding.php
/**
* Onboarding service - encapsulates the multi-step user invite / onboarding
* flow that was previously orchestrated inside the UserInvite controller.
+ *
+ * Deliberately NOT part of the JSON-RPC surface: every step trusts the invited-user record
+ * it is handed, so the only legitimate entry point is the invite-link controller.
*/
class Onboarding
{
Source: GitHub Commit 5605e5e
Detection Methods for CVE-2026-85990
Indicators of Compromise
- Unexpected administrator accounts created outside normal onboarding flows, especially accounts created via API key generation calls.
- JSON-RPC requests targeting leantime.rpc.api.api.createApiKeyWithProjects with a role parameter set to administrator values.
- Plugin install, enable, disable, or remove operations performed by non-admin user sessions.
- Presence of new or unknown plugins in the Leantime plugin directory that cannot be traced to an administrator action.
Detection Strategies
- Review web server access logs for POST requests to the JSON-RPC endpoint containing method names createApiKeyWithProjects, installPlugin, enablePlugin, disablePlugin, or removePlugin.
- Correlate authenticated session identifiers with the user role at request time to flag privilege mismatches on sensitive JSON-RPC methods.
- Alert on any JSON-RPC request carrying X-Requested-With: XMLHttpRequest where the originating user lacks administrator privileges but invokes an admin-scoped method.
Monitoring Recommendations
- Enable verbose application logging on the JSON-RPC dispatcher and ship logs to a centralized analytics backend for retention and query.
- Monitor the Leantime users table for new rows with administrator roles and alert on creation events outside of standard invite workflows.
- Track filesystem changes under the plugins directory to detect unauthorized plugin installation or removal.
How to Mitigate CVE-2026-85990
Immediate Actions Required
- Upgrade Leantime to version 3.10.0 or later, which closes the JSON-RPC account-takeover chain and enforces permissions on plugin management.
- Audit all Leantime user accounts for unexpected administrator roles and revoke any that cannot be attributed to a legitimate workflow.
- Review the installed plugin inventory and remove any plugins that were not approved by an administrator.
- Rotate API keys issued through Leantime, as attacker-created keys may have been scoped to arbitrary projects.
Patch Information
The fix is included in Leantime v3.10.0. The remediation combines the account-takeover fix in commit 5605e5e with plugin management hardening in commit 7ebf7a9. Full technical context is available in GHSA-54mm-6729-r5wp and pull requests #3583 and #3797.
Workarounds
- If immediate upgrade is not possible, restrict network access to the Leantime JSON-RPC endpoint using a reverse proxy or web application firewall rule that limits requests by source IP or session role.
- Temporarily disable self-service account registration and tighten invite flows to reduce the pool of low-privilege authenticated users that could reach the vulnerable methods.
- Deploy WAF signatures that block JSON-RPC request bodies referencing createApiKeyWithProjects, installPlugin, enablePlugin, disablePlugin, or removePlugin from non-administrator sessions.
# Example upgrade workflow
cd /var/www/leantime
php -r "echo file_get_contents('app/Core/Configuration/AppSettings.php');" | grep appVersion
git fetch --tags
git checkout v3.10.0
composer install --no-dev --optimize-autoloader
php bin/leantime db:update
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

