CVSS Calculator
CVSS v4.0 and v3.1 calculator. Select each metric, or paste a vector string such as the ones NVD lists, to get the score, severity rating, and vector string — entirely in your browser.
0.0
None
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N
About this tool
CVSS v4.0 & v3.1 Calculator
This calculator computes CVSS v4.0 and v3.1 scores. For v4.0 you set attack vector, attack complexity, attack requirements, privileges required, user interaction, and the confidentiality, integrity, and availability impact on both the vulnerable system and any subsequent system, plus an optional exploit-maturity threat metric. For v3.1 it covers the classic base metrics including scope.
What changed in v4.0: Scope is gone, replaced by separate impact metrics for the vulnerable and subsequent systems; a new Attack Requirements metric captures deployment conditions outside the attacker's control; User Interaction now distinguishes Passive from Active; and the score comes from a lookup over 270 expert-ranked MacroVectors with interpolation instead of a closed-form formula. v4.0 also names its scores: CVSS-B for base only, CVSS-BT when a threat metric is set. A v3.1 and a v4.0 score for the same flaw will not match, and that is expected.
CVSS v3.1 worked examples you can paste straight into the vector box: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H scores 9.8 Critical (a network-reachable flaw needing no privileges or user action that fully compromises the system). CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N scores 6.1 Medium (the classic reflected cross-site scripting shape: needs a victim to click, and Scope Changed because the impact lands in the victim's browser). CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H scores 7.8 High (a local privilege escalation by an already-logged-in user). The related-article links below walk through reading a vector metric by metric.
You get the numeric score, the severity rating, and the full vector string (for example, CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N) that you can paste into an advisory, a ticket, or a CVE entry.
Everything is calculated locally in your browser — nothing is uploaded, and the calculator works fully offline. The v3.1 math follows the FIRST specification, and the v4.0 scoring is a port of the FIRST reference implementation, checked against it across every base and threat combination.
How this differs from the FIRST and NVD calculators: those are the reference implementations, and for a score you put in an advisory, use them. This one exists for the moment-to-moment work around the score — triaging a queue of findings, checking what a vector string you found in someone else's advisory actually encodes, and comparing severity consistently across a program instead of a single CVE. It runs client-side, so it works on an air-gapped machine, on a pentest laptop without network, and with vulnerability details you wouldn't paste into a third-party site.
A note on how scoring gets misused: a base score is a property of the vulnerability, not of your environment. A 9.8 in a vacuum tells you nothing about your exposure — the same critical CVE matters differently on an internet-facing edge service and on an unreachable internal host. Pair the score with exposure context (that is the core argument of continuous threat exposure management), and let the vector string, not the number, carry the detail.
CVSS — the Common Vulnerability Scoring System, maintained by FIRST — is one lens among several. Where it fits alongside its neighbours: a CWE (Common Weakness Enumeration) ID classifies what kind of flaw a finding is, the CVSS base score grades how severe it would be in isolation, and SSVC (Stakeholder-Specific Vulnerability Categorization) decides whether your organization should act on it now. There is no such thing as a 'CWE calculator' or an 'SSVC calculator' — CWE is a lookup, and SSVC needs your exposure and mission context — but this calculator gives you the scoring half of that pipeline, and the vector string feeds directly into a triage decision.
When to use it
Score a finding for a vulnerability report
Select the base metrics for a vulnerability and get the score, severity, and vector string for your advisory or disclosure.
Triage findings consistently
Use the same calculator for every finding so severity ratings stay consistent across your team or program.
Re-derive a CVSS v3.1 score from an NVD entry
Paste the v3.1 vector string listed next to a CVE and confirm the base score and severity it produces.
Understand an existing CVSS vector
Work backwards from a vector string you found in an advisory and see which metric values produced the score.
Questions
Which CVSS version does this use?
Both CVSS v4.0 (the default) and v3.1, following the FIRST.org specifications. Paste a vector string and the calculator picks the right version automatically. v4.0 scoring covers the base metrics plus the Exploit Maturity threat metric.
Does it calculate temporal or environmental scores?
Only partly. v4.0 supports the Exploit Maturity threat metric (CVSS-BT). Environmental and supplemental metrics for v4.0, and temporal and environmental modifiers for v3.1, are not implemented yet, so the tool does not score them.
How do I calculate a CVSS v3.1 base score?
Pick the eight base metrics: attack vector, attack complexity, privileges required, user interaction, scope, and confidentiality, integrity and availability impact. The calculator combines them using the formula in the FIRST CVSS v3.1 specification and shows the score (0.0–10.0), the severity band, and the vector string. For example, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H gives 9.8 Critical. You can also paste a v3.1 vector and the metrics fill in for you.
Is my data uploaded?
No. All scoring math runs locally in your browser — nothing is sent to a server.
Why does the score differ from another calculator?
Scores differ when metric values are entered differently — for example, whether scope is changed, or how privileges required is interpreted. The vector string is the exact record of the values used.
How does CVSS relate to CWE?
They classify different things. A CWE ID (Common Weakness Enumeration) names the kind of flaw — SQL injection is CWE-89, an out-of-bounds write is CWE-787 — while the CVSS base score grades how severe that flaw would be in isolation. A CWE entry is a lookup in a classification catalogue, not something you compute, so a 'CWE calculator' isn't a thing: you look up the weakness, then score it. NVD pairs every CVE with both — a CWE ID for the weakness type and a CVSS base score for severity — and a finding's CWE can nudge the CVSS metrics (a weakness with no user interaction pushes attack complexity and UI values one way). This calculator is the scoring half of that pairing.
What is SSVC vs CVSS?
CVSS grades the vulnerability; SSVC (Stakeholder-Specific Vulnerability Categorization, also from Carnegie Mellon SEI) grades the decision. SSVC asks whether your organization should act now: is the vulnerability automated-exploitable, is the affected system in your production or decision-making chain, how exposed is it — and outputs Act / Attend / Track. So a CVE with a 9.8 CVSS score can legitimately land in 'Attend' if it's not exploitable in your environment, while a 7.5 that's exploited in the wild and sits on your edge gets 'Act'. SSVC isn't a calculator you feed a vector into — it needs your exposure and mission context — but the CVSS vector string you compute here is exactly the technical input its decision tree starts from.
What is a CVE score?
A 'CVE score' usually means the CVSS base score attached to a CVE entry (CVE IDs are the identifiers for publicly known vulnerabilities; the score grades their severity). NVD has long assigned a CVSS v3.1 base score to most CVEs — 9.8 for a textbook network-exploitable critical — and publishes the vector string next to it, so you can see exactly which metric values produced the number. Scores can differ between the vendor's advisory and NVD because they're scored by different analysts; the vector string tells you which one you're looking at. Enter that vector here to re-derive the score and severity rating.
What CVSS score is considered critical?
Under the qualitative severity scale shared by CVSS v3.1 and v4.0: 0.1–3.9 is Low, 4.0–6.9 is Medium, 7.0–8.9 is High, and 9.0–10.0 is Critical. The rating band matters less than the vector behind it — two 8.8s with different vectors are different problems.
What is a CVSS vector string?
The compact record of every metric value you selected, for example CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. It reads as: attack vector Network, attack complexity Low, privileges required None, user interaction None, scope Unchanged, and High impact on confidentiality, integrity, and availability. Anyone can re-derive your score from it, which is why advisories publish the vector alongside the number.
Should I use the FIRST calculator or this one?
Both compute the same math. Use the FIRST reference calculator when you need the authoritative score for a published advisory or CVE entry. Use this one for private triage work — client-side means nothing about your finding, your queue, or an undisclosed vulnerability leaves your machine, and it keeps working offline.
Related resources
Further reading
How to Read a CVSS Vector String
5 min read
CTEM Is Vulnerability Management That Stopped Lying to Itself
4 min read
Threat-Informed Defense Is Detection Engineering, Minus the Guessing
5 min read
Most Alerts Are Noise. Design for That.
2 min read
How to Red Team an AI Agent (Before It Gets Red Teamed for You)
10 min read