CVE-2026-15509
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been found in Leantime up to 3.8.0. This impacts the function editUser/addUser of the component JSON-RPC Endpoint. The manipulation of the argument role leads to improper authorization. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper authorization vulnerability in Leantime's JSON-RPC endpoint allows remote attackers to manipulate the 'role' argument in editUser/addUser functions to gain unauthorized access or elevate privileges beyond what their account should permit.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Leantime installationCheck for Leantime application files in your web root (typically in a /leantime or similar directory, or check for leantime-specific files like index.php with Leantime branding)Affected if Leantime is present in the environment
-
Determine Leantime versionLocate the version file or check the source code for a VERSION constant; common locations include /src/version.php, a VERSION file in the root directory, or the composer.json fileAffected if Installed version matches or precedes the vulnerable range (check vendor advisory for specific version numbers)
-
Verify JSON-RPC endpoint is exposedCheck if the JSON-RPC endpoint is accessible at /api/json-rpc or similar paths (inspect web server configuration for routes matching api/*, json-rpc*, or rpc* patterns)Affected if The JSON-RPC endpoint is reachable over the network without additional authentication barriers
-
Confirm user management functions are enabledInspect the JSON-RPC service configuration or API routing to confirm editUser and addUser functions are registered and active (look for routes handling user creation/modification in the API module)Affected if editUser/addUser functions are available in the JSON-RPC API
-
Check authorization controls on user role modificationReview the JSON-RPC handler code for editUser/addUser to verify if role parameter validation occurs; grep for role authorization logic in the relevant API controller filesAffected if No server-side role validation exists before allowing role parameter changes in user management functions
Your environment is affected if you are running a vulnerable Leantime version with the JSON-RPC endpoint exposed and user management functions accessible without proper role-based authorization checks on the role parameter.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper role-based access control (RBAC) validation in the JSON-RPC endpoint before allowing role modifications. Restrict access to the JSON-RPC user management functions until a vendor patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15509 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15509 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data