CVE-2026-58660

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-15. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 15, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Jul 15, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
Web page

Kanboard BoardAjaxController Missing Ownership Check via Drag-and-Drop | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kanboard-boardajaxcontroller-missing-ownership-check-via-drag-and-drop
GitHub pull request

fix(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/5853
Web page

Cross-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/5852
GitHub commit

commit 564cc30e1e36 (kanboard/kanboard)

Fix landed in kanboard/kanboard commit 564cc30e1e36 — awaiting tagged release

https://github.com/kanboard/kanboard/commit/564cc30e1e360959572e01e158734d9475c05903

Vendor 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 15× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 227 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-12 15:53 UTCEG score recompute
  4. 2026-10-11 19:36 UTCEG score recompute
  5. 2026-10-11 16:51 UTCEG score recompute
  6. 2026-10-11 14:14 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-08 16:39 UTCEG score recompute
  12. 2026-10-08 16:39 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-10-08 16:03 UTCEG score recompute
  14. 2026-10-08 16:03 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  21. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-01 12:40 UTCEG score recompute
  23. 2026-10-01 12:40 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  24. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 75 more
  1. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-09-28 08:44 UTCEG score recompute
  3. 2026-09-28 08:44 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-09-24 08:50 UTCEG score recompute
  8. 2026-09-24 08:50 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-09-23 03:16 UTCEG score recompute
  11. 2026-09-23 03:16 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  13. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-09-18 04:44 UTCEG score recompute
  15. 2026-09-18 04:44 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  16. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-14 10:56 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  21. 2026-09-13 23:12 UTCEG score recompute
  22. 2026-09-13 23:12 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-13 07:13 UTCEG score recompute
  25. 2026-09-13 07:13 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  26. 2026-09-12 13:02 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-09-11 21:45 UTCEG score recompute
  28. 2026-09-11 21:45 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-09-08 00:50 UTCEG score recompute
  33. 2026-09-08 00:50 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  34. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-09-06 13:28 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  37. 2026-09-05 20:50 UTCEG score recompute
  38. 2026-09-05 20:50 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  39. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  41. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  42. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-08-31 03:51 UTCEG score recompute
  44. 2026-08-31 03:51 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  46. 2026-08-30 16:03 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  47. 2026-08-30 03:52 UTCEG score recompute
  48. 2026-08-30 03:51 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  49. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  50. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  51. 2026-08-28 01:52 UTCEG score recompute
  52. 2026-08-28 01:52 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  54. 2026-08-27 12:40 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-08-26 23:31 UTCEG score recompute
  56. 2026-08-26 23:31 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  58. 2026-08-26 12:00 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-08-25 21:06 UTCEG score recompute
  60. 2026-08-25 21:06 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  62. 2026-08-25 08:48 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-08-24 20:41 UTCEG score recompute
  64. 2026-08-24 20:40 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  65. 2026-08-24 09:10 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-08-23 21:18 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  67. 2026-08-23 09:48 UTCEG score recompute
  68. 2026-08-23 09:48 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  69. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  70. 2026-08-22 22:19 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-08-22 10:49 UTCEG score recompute
  72. 2026-08-22 10:49 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  74. 2026-08-21 23:19 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1
  75. 2026-08-21 11:46 UTCGHSA enrichmentGHSA-f95x-r3pv-jh63 · GitHub severity HIGH · GitHub CVSS 8.1

Frequently asked(5)

What is CVE-2026-58660?
CVE-2026-58660 is a high-severity vulnerability; its CVE record was published on July 15, 2026. 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 projectid but never verifies that the supplied taskid actually belongs to that project. Because task identifiers…
When was CVE-2026-58660 made public?
CVE-2026-58660 was made public on July 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-58660 actively exploited?
CVE-2026-58660 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58660?
CVE-2026-58660 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58660?
An upstream fix for CVE-2026-58660 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-58660 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58660

Explore →

Is Your Infrastructure Affected by CVE-2026-58660?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.