Skip to content

Tools

CVSS 4.0 and 3.1 calculator

Score a vulnerability for your own environment. Paste a vector from the NVD or a vendor advisory, add the exploitation status and describe how the system runs in your organisation.

Everything runs in your browser. Nothing you enter is sent to a server.

Step 1

Base - vulnerability characteristics

Usually provided by the vendor or CNA

Base describes the vulnerability itself, regardless of deployment. Change this group only if you know the vendor rating is wrong. Describe differences in your environment in step 3.

AV - Attack Vector

The vulnerability can be exploited remotely over the network, including from the internet.

AC - Attack Complexity

The attack needs no protection bypass and can be repeated with a predictable result.

AT - Attack Requirements

Success does not depend on deployment conditions or system state.

PR - Privileges Required

The attacker needs no account and no authentication.

UI - User Interaction

The attack needs nobody except the attacker.

VC - Confidentiality - vulnerable system

Total loss of confidentiality or access to information with serious consequences, such as admin passwords.

VI - Integrity - vulnerable system

The attacker can modify data at will, or the modification has serious consequences.

VA - Availability - vulnerable system

Total loss of availability or a denial of service with serious consequences.

SC - Confidentiality - subsequent systems

No confidentiality impact beyond the vulnerable system.

SI - Integrity - subsequent systems

No integrity impact beyond the vulnerable system.

SA - Availability - subsequent systems

No availability impact beyond the vulnerable system.

Step 2

Threat - exploitation status

Filled in by you, from current data

Where to check: the CISA KEV catalogue, the vendor advisory, CISA Vulnrichment (SSVC) data in the NVD.

Missing data is scored as Attacked (the worst case), so this metric can only lower the score.

E - Exploit Maturity

Not Defined - scored as the worst case (Attacked).

Step 3

Environmental - your environment

Filled in by you, for a specific deployment

First state how important the system is, then describe how your deployment differs from the vendor's assumptions.

Security requirements

Usually the business owner of the system

What would losing the confidentiality, integrity or availability of this system mean for the organisation: a limited, serious or catastrophic effect?

CR - Confidentiality Requirement

Not Defined - scored as High.

IR - Integrity Requirement

Not Defined - scored as High.

AR - Availability Requirement

Not Defined - scored as High.

Modified Base metrics

Usually the system architect or administrator

Change only what is different and verified in your environment, for example by firewall rules. The default value takes the rating from Base.

MAV - Modified Attack Vector

As in Base: Network

MAC - Modified Attack Complexity

As in Base: Low

MAT - Modified Attack Requirements

As in Base: None

MPR - Modified Privileges Required

As in Base: None

MUI - Modified User Interaction

As in Base: None

MVC - Modified Confidentiality - vulnerable system

As in Base: High

MVI - Modified Integrity - vulnerable system

As in Base: High

MVA - Modified Availability - vulnerable system

As in Base: High

MSC - Modified Confidentiality - subsequent systems

As in Base: None

The Safety (S) value means a threat to human health or life. Use it when the foreseeable consequence is at least the Marginal category under IEC 61508. This is assessed by a process engineer, ideally based on a HAZOP or LOPA.

MSI - Modified Integrity - subsequent systems

As in Base: None

MSA - Modified Availability - subsequent systems

As in Base: None

Step 4

Supplemental - decision context

Provided by the vendor or by you

Does not change the score. This information helps with SSVC, with setting deadlines and with planning maintenance windows.

S - Safety

Not Defined - no information, the score is unchanged.

AU - Automatable

Not Defined - no information, the score is unchanged.

R - Recovery

Not Defined - no information, the score is unchanged.

V - Value Density

Not Defined - no information, the score is unchanged.

RE - Vulnerability Response Effort

Not Defined - no information, the score is unchanged.

U - Provider Urgency

Not Defined - no information, the score is unchanged.

Score

9.3Critical

CVSS-B Base metrics only: the score describes the vulnerability itself, as rated by the vendor.

Paste a vector from the NVD or a vendor advisory - the form fills itself in.

Next: the decision

A CVSS score describes severity. These tools help you decide what to do and by when:

Compare scenarios

Save up to 3 variants, for example Vendor, Plant A, Plant B. Scenarios stay in this browser only.

No saved scenarios.

9.3CriticalCVSS-B

How to use

  1. 1. Paste the vendor vector

    Copy the vector from the NVD, a vendor advisory or CISA and paste it into the vector field. The form sets the CVSS version and Base metrics for you.

  2. 2. Add Threat

    Check whether the vulnerability is in the CISA KEV catalogue and whether a public PoC exists. Without this information the calculator assumes the worst case.

  3. 3. Describe your environment

    State how important the system is and mark verified differences, for example no access from the internet. Save variants as scenarios and compare the results.

Common questions about CVSS

How does CVSS 4.0 differ from 3.1?

Version 4.0 adds the Attack Requirements (AT) metric, replaces Scope by separating impact on the vulnerable system from impact on subsequent systems, introduces the Supplemental group and replaces Temporal with the Threat group and its single metric E. The score no longer comes from a weighted formula but from expert ratings of 270 groups of similar vectors. Version 4.0 produces a single score labelled CVSS-B, CVSS-BT, CVSS-BE or CVSS-BTE.

Why can the Threat metric only lower the score?

Missing exploitation data (E:X) is scored as Attacked, the worst case. Setting E:A confirms that assumption, while E:P or E:U relaxes it. This way a score without data never understates severity. Environmental metrics work in both directions: impact on human safety, for example, can raise the score.

Can I compare CVSS 3.1 and 4.0 scores?

Not directly. The two versions calculate scores differently, so the same vulnerability can score 7.3 in version 3.1 and 6.9 in version 4.0. Compare vectors and scores within one version. FIRST only provides a conversion from 4.0 to 3.1, which is why the calculator does not convert 3.1 to 4.0 automatically.

Where do I get data for the Threat metric?

Most often from the CISA KEV catalogue (confirmed attacks), vendor advisories, CISA Vulnrichment data published in the NVD, and information on public exploits and Metasploit modules. Exploitation status changes over time, so it is worth refreshing automatically. EPSS gives the probability of exploitation within 30 days - use it alongside CVSS, not as the value of E.

CVSS is owned by FIRST.Org, Inc. and used with permission. MacroVector tables and interpolation algorithm: © FIRST.ORG, Inc., Red Hat and contributors, BSD-2-Clause licence.

Book a call