CVE-2026-72563

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A broken access control vulnerability in BadChoice Handesk as of 2026-07-10 allows any authenticated agent to overwrite lead records belonging to other teams via the LeadsController@update endpoint. The endpoint performs no authorization check, and the Lead model has guarded set to an empty array making all columns mass-assignable. An attacker with any agent account can corrupt lead data across team boundaries.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
No patch confirmed yet.
generic

GitHub - BadChoice/handesk: A Powerful Laravel Help Desk and Lead Management App · GitHub

https://github.com/BadChoice/handesk

Vendor Advisories for CVE-2026-72563(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 27× in last 7d / 41× 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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 20:40 UTCGHSA enrichment
  3. 2026-08-20 07:41 UTCGHSA enrichment
  4. 2026-08-19 18:42 UTCEG score recompute
  5. 2026-08-19 18:42 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 04:15 UTCGHSA enrichment
  8. 2026-08-18 15:17 UTCEG score recompute
  9. 2026-08-18 15:17 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 01:18 UTCEG score recompute
  13. 2026-08-18 01:17 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 12:16 UTCGHSA enrichment
  16. 2026-08-16 23:17 UTCEG score recompute
  17. 2026-08-16 23:17 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 10:17 UTCEG score recompute
  21. 2026-08-16 10:17 UTCGHSA enrichment
  22. 2026-08-16 02:15 UTCEPSS rescore
  23. 2026-08-15 21:19 UTCGHSA enrichment
  24. 2026-08-15 08:20 UTCEG score recompute
  25. 2026-08-15 08:20 UTCGHSA enrichment
Show 16 more
  1. 2026-08-15 01:31 UTCEPSS rescore
  2. 2026-08-14 19:20 UTCGHSA enrichment
  3. 2026-08-14 06:21 UTCEG score recompute
  4. 2026-08-14 06:21 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 17:22 UTCGHSA enrichment
  7. 2026-08-13 04:23 UTCGHSA enrichment
  8. 2026-08-12 15:24 UTCEG score recompute
  9. 2026-08-12 15:24 UTCGHSA enrichment
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 02:24 UTCGHSA enrichment
  12. 2026-08-11 13:25 UTCEG score recompute
  13. 2026-08-11 13:25 UTCGHSA enrichment
  14. 2026-08-11 12:23 UTCEG score recompute
  15. 2026-08-11 11:22 UTCEG score recompute
  16. 2026-08-11 11:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72563?
CVE-2026-72563 is a high vulnerability published on August 11, 2026. A broken access control vulnerability in BadChoice Handesk as of 2026-07-10 allows any authenticated agent to overwrite lead records belonging to other teams via the LeadsController@update endpoint. The endpoint performs no authorization check, and the Lead model has guarded set to an empty array…
When was CVE-2026-72563 disclosed?
CVE-2026-72563 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72563 actively exploited?
CVE-2026-72563 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 89.7% of all scored CVEs.
What is the CVSS score of CVE-2026-72563?
CVE-2026-72563 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-72563?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72563, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-72563?

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

Start Free Scan →Browse All CVEs