dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-58660

HIGH · 8.1 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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 · unedited
Kanboard through 1.2.52, fixed in commit 564cc30, BoardAjaxController save() method (used by the kanban board drag-and-drop endpoint) validates the caller's role on the attacker-supplied project_id but never verifies that the supplied task_id actually belongs to that project. Because task identifiers are sequential integers shared across the entire instance, any authenticated user who is a member of at least one project can enumerate and move (corrupt/hide) tasks belonging to any other project on the same instance, including private projects they have no membership or role on.

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 · high confidence

Kanboard's BoardAjaxController save() method validates user role permissions on a project but fails to verify that the task_id being moved actually belongs to that project. Since task IDs are sequential integers shared globally across the instance, any authenticated user who is a member of at least one project can enumerate task IDs and move, corrupt, or hide tasks from any other project on the instance, including private projects they have no access to.

MitigationApply the fix from commit 564cc30 which adds proper task-project ownership verification in the save() method to ensure the task_id belongs to the project_id before allowing any move operations.

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Kanboard version
    Open the file 'VERSION' in the Kanboard root directory, or access the dashboard and look for the version number in the footer or about section
    Affected if version is older than the version containing fix commit 564cc30 (verify against official release notes)
  2. Verify BoardAjaxController save() method code
    Locate the file containing BoardAjaxController class and its save() method (typically in src/Controller/BoardAjaxController.php). Inspect the method to see if it contains a check verifying that the task belongs to the project before performing move operations
    Affected if the save() method lacks a database query or logic that validates task_project.task_id matches the provided project_id parameter
  3. Confirm user authentication requirement
    Verify that the application requires authentication for accessing the BoardAjaxController endpoints. Check if unauthenticated requests are rejected by the controller or application middleware
    Affected if authenticated users can access the BoardAjaxController save() endpoint without additional project-level permissions beyond basic project membership
  4. Test task enumeration and cross-project access
    As an authenticated user who is a member of at least one project, use browser developer tools or an HTTP client to intercept a task move request. Modify the task_id parameter to a value that belongs to a different project (task IDs are sequential integers), and submit the request
    Affected if the application accepts the modified request and moves, hides, or modifies a task from a project the user is not a member of

A user is affected if they run a Kanboard version where BoardAjaxController save() does not verify that the task_id belongs to the specified project_id, allowing any authenticated project member to access tasks across all projects via ID enumeration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the fix from commit 564cc30 which adds proper task-project ownership verification in the save() method to ensure the task_id belongs to the project_id before allowing any move operations.

Recommended fix Moderate confidence

Latest stable release after 1.2.52 containing commit 564cc30 (verify the release notes for inclusion)

  1. 1. Identify the current Kanboard version by checking the installation directory or admin interface
  2. 2. Review the fix in commit 564cc30 on the Kanboard GitHub repository (github.com/kanboard/kanboard) to understand the code changes
  3. 3. If a newer stable version containing the fix is available, plan and schedule the upgrade during a maintenance window
  4. 4. Before upgrading, backup the Kanboard database and files
  5. 5. Upgrade to the latest stable release that includes the fix for this IDOR vulnerability
  6. 6. After upgrade, verify that authenticated users can only modify tasks within projects they are members of
  7. 7. Test the board drag-and-drop functionality to confirm normal operation
Caveat Review release notes for any breaking changes between 1.2.52 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58660 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58660 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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