— Developer Tools

Free CVSS Calculator

Paste a CVSS vector to get its score and severity, see every metric in words, or export the JSON record.

— Samples
Score 9.8Severity CriticalValid
Live

What is a CVSS Calculator?

CVSS, the Common Vulnerability Scoring System, turns a vulnerability’s characteristics into a score from 0 to 10. Security advisories publish it as a vector such as CVSS:3.1/AV:N/AC:L/…. This calculator scores those vectors and explains what each part means.

It scores CVSS 4.0, 3.1, 3.0 and 2.0 with the ae-cvss-calculator library, which follows FIRST’s specifications. Base, threat or temporal, and environmental scores are shown when the vector defines them, with severity bands, the 4.0 nomenclature, every metric in words, and the JSON record NVD and CVE use.

Key Features

Four Versions

CVSS 4.0, 3.1, 3.0 and 2.0, recognised from the vector itself.

Every Score

Base, impact and exploitability, temporal or threat, and environmental where defined.

Metrics in Words

Each metric and value named, from Attack Vector to Provider Urgency.

JSON Record

The CVSS JSON schema output, as vulnerability databases publish it.

Nothing Uploaded

Vectors are scored in your browser, so unpublished findings stay private.

Perfect for everyone

  • Security engineers
  • Vulnerability managers
  • Penetration testers
  • Bug bounty hunters and developers triaging advisories

How to Use the CVSS Calculator

Paste a vector from an advisory or build one yourself.

1

Get the Vector

From an NVD entry, a vendor advisory, a scanner report or your own assessment.

2

Paste It

The version is read from the prefix; 2.0 vectors have none.

3

Read the Score

Score shows the effective score and severity, with each sub-score.

4

Check the Metrics

Metrics explains every value, and JSON exports the record.

Worked Examples

Vectors, Scored

Each row is a CVSS vector as advisories publish it, and each answer is this calculator’s output in the mode on the chip. The first is the vector behind many critical remote code execution advisories.

REF_001The classic 9.8

“CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H”

REF_002The same flaw in CVSS 4.0

“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”

REF_003Every metric named

“CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C/CR:H/IR:M/AR:L”

REF_004Adjusted with threat and environment

“CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C/CR:H/IR:M/AR:L”

REF_005A reflected XSS in 3.0

“CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N”

REF_006A CVSS 2.0 vector

“AV:N/AC:L/Au:N/C:P/I:P/A:P”

REF_0074.0 with no known exploit

“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/E:U”

REF_008The CVSS JSON record

“CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H”

REF_009Base metrics missing

“CVSS:3.1/AV:N/AC:L/PR:N/UI:N”

REF_010A version that doesn’t exist

“CVSS:5.0/AV:N/AC:L”

Base Metrics

The CVSS 3.1 Base Metrics

Eight base metrics describe a vulnerability itself. Learn them and most vectors read at a glance.

01 / AV

AV, Attack Vector

How far away the attacker can be: network, adjacent, local or physical.

“What is AV:N?”

02 / AC

AC, Attack Complexity

Whether conditions outside the attacker’s control must line up.

“What does AC:H mean?”

03 / PR

PR, Privileges Required

What access the attacker needs first: none, low or high.

“Which is worst for defenders?”

04 / UI

UI, User Interaction

Whether a user must do something, such as click a link.

“What is UI:R?”

05 / S

S, Scope

Whether the impact reaches beyond the vulnerable component.

“What raises the score?”

06 / C

C, I and A

Impact on confidentiality, integrity and availability: high, low or none.

“What does C:H mean?”

07 / SEVERITY

Severity Bands

None 0.0, Low 0.1 to 3.9, Medium 4.0 to 6.9, High 7.0 to 8.9, Critical 9.0 to 10.0.

“Is 9.0 High or Critical?”

08 / TEMPORAL

Temporal Metrics

Exploit maturity, remediation level and report confidence lower the base score.

“Can temporal metrics raise it?”

09 / ENVIRONMENTAL

Environmental Metrics

Your own security requirements and modified base metrics adjust it for you.

“Who sets them?”

10 / THE

The Vector

All metrics as KEY:VALUE pairs after the version prefix.

“What starts a 3.1 vector?”

What Changed in CVSS 4.0

FIRST published CVSS 4.0 in 2023 to fix long-standing complaints about 3.1. The vector looks familiar but reads differently, and the same flaw often scores differently.

Attack Requirements

A new AT metric covers conditions in the target, separate from Attack Complexity.

Passive and Active Interaction

User Interaction splits into Passive and Active, depending on what the user must do.

Vulnerable and Subsequent Systems

Scope is gone. Impacts are scored separately for the vulnerable system and systems beyond it.

Threat Metrics

Temporal metrics shrink to Exploit Maturity, with values such as Attacked and Unreported.

Supplemental Metrics

Safety, Automatable, Recovery and others add context without changing the score.

Nomenclature

CVSS-B, BT, BE and BTE say which metric groups a score includes.

Using Scores Well

A score is a summary of severity, not of risk. These habits keep CVSS useful when you prioritise patches and write advisories.

Tip 01

Severity Isn’t Risk

A critical flaw in a system you don’t run matters less than a medium one in your login page.

Tip 02

Add the Environment

Environmental metrics fit the score to your systems. Without them it’s the vendor’s view.

Tip 03

Watch for Exploitation

Exploit maturity and lists such as CISA KEV say more about urgency than the base score.

Tip 04

Compare Like With Like

A 3.1 score and a 4.0 score for the same flaw can differ, so note the version.

Tip 05

Publish the Vector

Always share the vector with the score, so others can see and adjust each choice.

Tip 06

Rescore When Facts Change

A new exploit or a vendor fix changes threat metrics, so update the score.

When to Use a CVSS Calculator

Whenever a vulnerability needs a defensible score.

Triaging Advisories

Read the vector behind an NVD score to see why it’s critical.

Writing Reports

Score a penetration test finding and show the vector behind it.

Bug Bounty Submissions

Back a severity claim with a vector the triager can check.

Patch Prioritisation

Adjust base scores with environmental metrics for your own estate.

Learning CVSS

See how each metric moves the score in 3.1 and 4.0.

CVSS Pitfalls

Mistakes that produce misleading scores.

Tip 01

Scoring the Worst Case

Score the vulnerability as it is, not what an attacker might chain it with.

Tip 02

Misreading Scope

In 3.1, S:C only applies when impact crosses a security boundary, which is rarer than it seems.

Tip 03

Network by Default

AV:N needs exploitation across the network. A local file parser is often AV:L.

Tip 04

Mixing Versions

Pasting 3.1 metric names into a 4.0 vector, or the reverse, gives an invalid vector.

Tip 05

Rounding by Hand

CVSS 3.x rounds up to one decimal in a specific way, so let the calculator do it.

Tip 06

Ignoring 2.0 Bands

CVSS 2.0 has no Critical band. NVD rated 7.0 and above as High.

Frequently Asked Questions