Common Vulnerability Scoring System (CVSS)
Abbreviation: CVSS
Pronunciation: KAH-mun vul-nur-uh-BIH-lih-tee SKAW-ring SIS-tum (C-V-S-S)
Also known as: Common Vulnerability Scoring System, CVSS
Definition
CVSS is an open framework for describing software vulnerability characteristics and calculating standardized severity scores and vector strings. Defenses against Common Vulnerability Scoring System (CVSS) combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Overview
Meaning and scope
CVSS is an open framework for describing software vulnerability characteristics and calculating standardized severity scores and vector strings. Defenses against Common Vulnerability Scoring System (CVSS) combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Mechanism and operation
The Common Vulnerability Scoring System provides structured metrics for communicating the technical severity and context of software vulnerabilities. A vector records metric values, while a numerical score and qualitative rating summarize the selected characteristics under a specified CVSS version. CVSS 4.0 separates Base, Threat, Environmental, and Supplemental metric groups. A CVSS score measures severity, not organizational risk or remediation priority by itself. Teams should combine it with exploit activity, asset importance, exposure, available controls, business impact, and deployment context before deciding when and how to remediate. CVSS standardizes vulnerability severity, but prioritization still requires asset context, exposure, threat intelligence, and the stated scoring version.
Practical payment example
An engineer records a vulnerability’s CVSS characteristics but also weighs exposed assets and exploitability in the actual payment environment before prioritizing remediation.
Operational checks
Assessment of Common Vulnerability Scoring System (CVSS) should trace CVSS is an open framework for describing software vulnerability characteristics and calculating standardized severity scores and vector strings from prerequisite and entry point through observable impact on the affected service. A theoretical weakness or scanner result involving CVSS is an open framework for should not be reported as exploitation without corroborating logs, transactions, or configuration evidence.
Distinctions and limits
Earlier versions use different terminology and formulas, so reports should always state the version and full vector rather than comparing numbers without methodological context. Prevention, detection, containment, and recovery for the Common Vulnerability Scoring context should be tested against the architecture associated with CVSS is an open framework for.
Related reading
Related definitions: Vulnerability, risk.
Example
An engineer records a vulnerability’s CVSS characteristics but also weighs exposed assets and exploitability in the actual payment environment before prioritizing remediation.
Comparison
Earlier versions use different terminology and formulas, so reports should always state the version and full vector rather than comparing numbers without methodological context. A CVSS score measures severity, not organizational risk or remediation priority by itself.
Key Takeaway
CVSS standardizes vulnerability severity, but prioritization still requires asset context, exposure, threat intelligence, and the stated scoring version.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)