Visual Studio Elevation of Privilege Vulnerability

According to the CVSS metric, user interaction is required (UI:R) and privileges required is Low (PR:L). What does that mean for this vulnerability?
An authenticated attacker could create a malicious extension and then wait for an authenticated user to create a new Visual Studio project that uses that extension. The result is that the attacker could gain the privileges of the user.

What privileges could be gained by an attacker who successfully exploited the vulnerability?
An attacker who successfully exploited this vulnerability could gain administrator privileges.

According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability?
Successful exploitation of this vulnerability requires an attacker to gather information specific to the environment and take additional actions prior to exploitation to prepare the target environment.

According to the CVSS metrics, successful exploitation of this vulnerability could lead to some loss of availability (A:L)? What does that mean for this vulnerability?
The performance can be interrupted and/or reduced, but the attacker cannot fully deny service.

Security updates
17.10.2 — https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes
15.9.63 — https://docs.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes
16.11.37 — https://docs.microsoft.com/en-us/visualstudio/releases/2019/release-notes-v16.11