# CVE, CVSS, and Patch Priority — A Plain English Guide

> Log4Shell. Heartbleed. EternalBlue. These vulnerability names ended up in mainstream news. But what do they actually mean? And when your scanner returns 200 vulnerabilities on a Monday morning, how do you decide which one to fix first? This post answers both questions.

## What is a CVE?

CVE stands for Common Vulnerabilities and Exposures. It's a standardised naming system that gives every publicly known software vulnerability a unique identifier. The format is: `CVE-YEAR-NUMBER`.

For example, `CVE-2021-44228` is Log4Shell — the critical vulnerability in the Log4j Java library discovered in December 2021. The year tells you when it was assigned, and the number is sequential. When you see a CVE ID, you can look it up instantly on nvd.nist.gov for the full technical details.

CVEs are assigned by organisations called CNAs (CVE Numbering Authorities) — companies like Microsoft, Google, and Red Hat can assign CVE IDs to vulnerabilities they discover in their own products.

## What is CVSS?

CVSS (Common Vulnerability Scoring System) is a standardised way to score the severity of a vulnerability on a scale from 0.0 to 10.0. The higher the score, the more severe.

- **0.0:** None
- **0.1 – 3.9:** Low
- **4.0 – 6.9:** Medium
- **7.0 – 8.9:** High
- **9.0 – 10.0:** Critical

The score is calculated from several factors: how easy is the vulnerability to exploit (over the network vs requires physical access)? Does it require authentication? What's the impact on confidentiality, integrity, and availability if exploited? Log4Shell scored 10.0 — exploitable remotely, no authentication required, full system takeover possible.

## CVSS alone is not enough for prioritisation

Here's the problem: a CVSS score measures the theoretical worst case. It doesn't tell you whether the vulnerability is actually being exploited in the wild right now, whether your specific configuration is vulnerable, or whether the affected system is critical to your business.

A CVSS 9.8 vulnerability in a library that isn't installed on any of your systems is far less urgent than a CVSS 7.0 vulnerability in a public-facing server being actively exploited today.

## EPSS — a smarter prioritisation signal

EPSS (Exploit Prediction Scoring System) is a newer metric that predicts the probability of a CVE being exploited in the wild within the next 30 days, based on historical exploitation data and threat intelligence. A CVE with a CVSS of 9.8 but an EPSS of 0.3% (low probability of exploitation) may be less urgent than a CVSS 6.5 with an EPSS of 72%. Check EPSS scores at first.org/epss.

## A practical prioritisation framework

When your scanner drops 200 findings on a Monday morning, use this mental model to decide what gets fixed first:

1. **Is it being actively exploited right now?** Check CISA's Known Exploited Vulnerabilities catalogue (cisa.gov/kev). If it's on that list, it's your top priority — regardless of CVSS score.
2. **Is the vulnerable system internet-facing?** External exposure dramatically increases risk.
3. **Is the system business-critical?** Downtime on a payment processor is far more impactful than downtime on an internal wiki.
4. **What is the CVSS score?** Critical and High get patched first among similar-priority systems.
5. **Can you apply a compensating control if you can't patch now?** Firewall rules, disabling the vulnerable feature, adding monitoring — these buy time.
