WiFiman Desktop CVE-2026-119251

Exploitation requires the attacker to already have local access to a macOS host running Ubiquiti WiFiman Desktop AND to already hold high privileges on that host (per description and CVSS PR:H); it is a local-only escalation with no remote or unauthenticated path and no user interaction. Limiting factors: the pre-existing high-privilege local foothold is the primary barrier, the affected software must be installed and running on macOS, and there is no network-exploitable surface. The specific feature or component whose access control is improperly enforced is not detailed in the available sources.

This is a moderate-severity, locally-exploitable privilege-escalation issue (CVSS 6.7). The CVSS vector AV:L/AC:L/PR:H/UI:N is internally consistent with the description: the attacker must already have local access and high privileges on the macOS host, so this is not a remotely reachable or initial-access flaw - it is a post-compromise escalation primitive. The vuln.today decision label is 'this_month' rather than act_now/emergency, which aligns with the signal picture: no CISA KEV listing, no EPSS score supplied, and no public exploit or PoC reference in the input. The main caveats are that EPSS was not provided (exploitation probability cannot be quantified) and the PR:H requirement means an attacker already holds elevated rights, which narrows the practical value of the escalation and keeps real-world urgency moderate. There is a tension worth noting: with PR:H already required, the incremental impact of 'escalate privileges' depends on what boundary is crossed (e.g., high-privileged user to root/system) - the advisory text does not specify the exact privilege transition, so the C:H/I:H/A:H impact rating should be verified against Ubiquiti's bulletin. Overall this is a genuine but not emergency priority: schedule the vendor update this patch cycle.

A malicious local user or process that already holds high privileges on a macOS machine running WiFiman Desktop abuses the improper access control weakness to escalate to a higher privilege level on the host. Because the attack vector is local with low complexity and no user interaction, exploitation is straightforward for anyone with the prerequisite local foothold, but it cannot be launched remotely. No public exploit code or PoC reference is identified at time of analysis.