CyberKit

Tool Respond & Report

Risk Scoring

Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.

Two numbers people ask for during an incident: how bad is the vulnerability, and how bad is the incident. One tab scores a CVSS v3.1 vector, the other scores an incident across five dimensions. Both show their work.

This runs in your browser. Nothing you type or open is uploaded.

How to read it

CVSS scores the flaw, not your exposure to it. A 9.8 on a server nobody can reach may matter less than a 6.5 on your email gateway.

The incident score is a weighted sum with a few overrides, such as confirmed data loss. The reasoning table shows which choice moved it.

Copy either result into the Report Generator so the number and its reasoning travel together.

Tab by tab

CVSS v3.1

CVSS puts a 0.0 to 10.0 number on how severe a vulnerability is. The vector string is the reproducible record of how that number was reached, and it says more than the score does.

Pick the eight Base metrics, or paste a vector. The score, the severity band, and the vector all update together.

This is CVSS v3.1 Base only. It rejects 3.0 and 4.0 vectors rather than guessing, and it has no Temporal or Environmental metrics, so the score is the vulnerability's own severity, not its risk in your environment.

Base metrics
MetricWhat it asksValues
Attack Vector (AV)How the vulnerable component is reached.N = Network, A = Adjacent, L = Local, P = Physical
Attack Complexity (AC)Conditions beyond the attacker's control that must exist first.L = Low, H = High
Privileges Required (PR)The access level an attacker must already hold before the attack.N = None, L = Low, H = High
User Interaction (UI)Whether a human other than the attacker must take an action.N = None, R = Required
Scope (S)Whether the exploit's impact can spread beyond the vulnerable component's own security authority.U = Unchanged, C = Changed
Confidentiality (C)Impact to the confidentiality of data the vulnerable component manages.H = High, L = Low, N = None
Integrity (I)Impact to the trustworthiness of data the vulnerable component manages.H = High, L = Low, N = None
Availability (A)Impact to the availability of the vulnerable component itself.H = High, L = Low, N = None
Incident severity

There is no industry-standard formula for incident severity the way CVSS is standard for vulnerabilities. This is one explicit model with its weights in the open, meant to structure a judgment or sanity-check one.

Rate each dimension. The weighted total is scaled to 0 to 100, with SEV-1 at 70, SEV-2 at 45, and SEV-3 at 20.

A weighted average can quietly average away a catastrophe, so a few conditions decide on their own. They can only raise a severity, never lower it, and the tool says when one did.

It does not replace your organization's own definitions.

Dimensions
DimensionWeightWhat it asks
Scope1.2How much of the estate is involved?
Data sensitivity1.3What is the most sensitive data in scope?
Business impact1.2What is the effect on operations right now?
Access obtained1.3What level of access has the attacker demonstrably reached?
Recoverability1How hard is it to get back to a known-good state?

Terms behind it

Sources

  • FIRST: CVSS v3.1 Specification Document. The authoritative specification this page's calculator implements: the three metric groups (Section 1.1), every Base metric definition and numeric weight, the Base Score equations (Section 7.1), the qualitative severity bands (Section 5), and the Roundup function in Appendix A.
  • FIRST: CVSS v3.1 User Guide. The companion document to the specification: visual scoring rubrics for each metric, plus the guidance a spec alone leaves out. How to score vulnerability chains, firewall-protected components, and vulnerabilities in libraries, and how to decide Scope in ambiguous cases.
  • FIRST: CVSS v3.1 Examples. FIRST's own 31 worked examples. Real CVEs with a full justification for every metric choice, the resulting vector string, and the published score. The source of the worked examples on this page, and the reference answers this site's own test suite checks its implementation against.
  • FIRST: CVSS v3.1 Calculator. FIRST's official v3.1 calculator. Worth going to directly for the two metric groups this page deliberately does not implement: Temporal (exploit maturity, remediation level, report confidence) and Environmental (your own C/I/A requirements plus per-metric overrides).
  • FIRST: CVSS v4.0 Specification Document. The current major version of the standard, and a substantially different scoring system: new Attack Requirements metric, Passive/Active User Interaction values, impact split across vulnerable and subsequent systems, an optional Supplemental group, and the CVSS-B/BT/BE/BTE nomenclature. This page scores v3.1 only.
  • FIRST: EPSS (Exploit Prediction Scoring System). A data-driven model estimating the probability that a published CVE will be exploited in the wild within the next 30 days, published daily as free scores and percentiles. The exploitation-likelihood dimension a CVSS Base Score deliberately does not measure.

Worth using too

  • Vulnerability-Lookup (CIRCL). A free, open-source vulnerability platform run by CIRCL, Luxembourg's national CERT: correlates advisories across national databases, CSAF providers, and community feeds, and adds real-world "sightings" plus several KEV catalogs, which is the evidence a Base Score alone leaves you needing.

All tools