BadChoice Handesk - Broken Access Control

Answer in brief

CVE-2026-72563 records a High severity (CVSS 8.1) vulnerability in BadChoice Handesk - Broken Access Control. The current sources do not mark it as known exploited. The current feed maps BadChoice/Handesk (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 11, 2026Updated Aug 28, 2026Source checked Sep 25, 2026First seen by HOL Aug 11, 2026Material review Aug 28, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps BadChoice/Handesk (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
BadChoice/Handeskgeneric	0	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for BadChoice/Handesk.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Aug 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 28, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 11, 2026

Sources and claim methodology

GitHub security advisorygithub.com

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.