- 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:H)
- They need powerful rights—admin, root, or similar—before this pays off.
- User interaction (UI:R)
- A real person has to do something—click, install, enable—otherwise it doesn’t land.
- Scope (S:U)
- Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
- Confidentiality (C:H)
- Serious risk that confidential data gets exposed in a big way.
- Integrity (I:H)
- They could widely tamper with or forge data—trust in the data is badly hurt.
- Availability (A:L)
- Might cause slowdowns, glitches, or partial disruption—not a full brick.