Common Vulnerability Scoring System
Also called CVSS.
An open framework that scores vulnerability severity from 0 to 10.
What it is
An open standard, maintained by FIRST, for rating the severity of a vulnerability on a 0-10 scale. It combines base metrics (intrinsic traits like attack vector and impact) with optional threat and environmental metrics that adjust the score for real-world exploitation and a specific deployment.
Why it matters
CVSS gives a consistent, transparent severity language across vendors, but the base score alone reflects worst-case potential, not actual risk, which practitioners pair it with exploitation data and asset context before prioritizing.
In practice
Treating a CVSS 9.8 base score as a starting point, then checking exploitation likelihood and asset exposure before scheduling the patch.
What to look for
- Base score and the vector string behind it.
- Attack vector, privileges and user interaction.
- Version differences between 3.1 and 4.0.
Common mistake
Patching by score alone. Severity is not the same as likelihood of exploitation.
Use it in CyberKit
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Nessus Commercial
A vulnerability scanner that checks hosts for known flaws and missing patches.
-
Qualys VMDR Commercial
A cloud platform that scans assets and ranks vulnerabilities for patching.
-
OpenVAS Open source
An open source vulnerability scanner with a large set of checks.
-
Nuclei Open source
Runs community templates that test for specific, newly published flaws.
Read next
- Common Vulnerabilities and Exposures: The universal ID scheme that assigns a unique identifier to each public vulnerability.
- Exploit Prediction Scoring System: A data-driven probability that a given CVE will be exploited in the next 30 days.
- Known Exploited Vulnerabilities: A curated list of CVEs with reliable evidence of active exploitation in the wild.