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.
CVE-2026-58660
This high-severity CVE scores 8.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026Kanboard BoardAjaxController Missing Ownership Check via Drag-and-Drop | Advisories | VulnCheck
https://www.vulncheck.com/advisories/kanboard-boardajaxcontroller-missing-ownership-check-via-drag-and-dropfix(board): verify task belongs to project before moving
Fix merged in kanboard/kanboard PR #5853 on 2026-07-14 — awaiting tagged release
https://github.com/kanboard/kanboard/pull/5853Cross-project task hijack via missing project ownership check in BoardAjaxController drag-and-drop endpoint · Issue #5852 · kanboard/kanboard · GitHub
https://github.com/kanboard/kanboard/issues/5852commit 564cc30e1e36 (kanboard/kanboard)
Fix landed in kanboard/kanboard commit 564cc30e1e36 — awaiting tagged release
https://github.com/kanboard/kanboard/commit/564cc30e1e360959572e01e158734d9475c05903Vendor Advisories for CVE-2026-58660(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-15 17:29 UTCEG score recompute
- 2026-07-15 17:28 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-639
- CVE-2018-25270EG 9.8CRITICAL
- CVE-2017-20223EG 9.8CRITICAL
- CVE-2019-25487EG 9.8EPSS 94%CRITICAL
- CVE-2019-25235EG 9.8CRITICAL
- CVE-2020-16088EG 9.8CRITICAL
- CVE-2019-15310EG 9.8EPSS 94%CRITICAL
- CVE-2020-11658EG 9.8CRITICAL
- CVE-2019-15913EG 9.8CRITICAL
- CVE-2019-16340EG 9.8EPSS 97%CRITICAL
- CVE-2019-13360EG 9.8EPSS 98%CRITICAL
Frequently asked(4)
What is CVE-2026-58660?
When was CVE-2026-58660 disclosed?
What is the CVSS score of CVE-2026-58660?
How do I remediate CVE-2026-58660?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58660
Is Your Infrastructure Affected by CVE-2026-58660?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.