- Attack vector (AV:L)
- They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
- Attack complexity (AC:L)
- Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
- Privileges required (PR:L)
- A normal user session is enough; they don’t have to be admin.
- User interaction (UI:N)
- Nobody has to click “OK” or open a trap file; it can work without a victim helping.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:L)
- Some sensitive info could get out, but not a total data dump.
- Integrity (I:L)
- Attackers could change some data, but it’s limited—not everything goes.
- Availability (A:H)
- Could take the service down hard or make it unusable for people who depend on it.