Free tool · runs in your browser

CVSS Calculator

Compute the CVSS 4.0 or 3.1 score of a vulnerability, build the vector and share it by link.
Local processing No data sent No account Reporting

Powered by ae-cvss-calculator (metaeffekt) · Apache-2.0

01Exploitability
Attack Vector (AV) Where the attacker can exploit the vulnerable system from.
Attack Complexity (AC) Security measures the attacker must defeat (ASLR, DEP, a secret to guess).
Attack Requirements (AT) Deployment or execution conditions the attack depends on (race condition, on-path network position).
Privileges Required (PR) Level of access needed before the attack.
User Interaction (UI) Passive: the victim only views a page. Active: they must click, install or accept something.
02Vulnerable system impact
Confidentiality (VC) On the vulnerable system.
Integrity (VI) On the vulnerable system.
Availability (VA) On the vulnerable system.
03Subsequent system impact
Confidentiality (SC) On subsequent systems (victim’s browser, host, other services).
Integrity (SI) On subsequent systems.
Availability (SA) On subsequent systems.
Advanced: threat, environmental, supplemental 0 set

Optional. “Not defined” (X) keeps the default. Threat and environmental metrics give the CVSS-BT, BE or BTE score; supplemental metrics describe the flaw without changing the score.

04Threat
Exploit Maturity (E) Attacked: exploitation reported or a public tool exists. PoC: a public proof of concept exists.
05Security requirements
Confidentiality Requirement (CR) How much the confidentiality of this asset matters to the organisation.
Integrity Requirement (IR) How much the integrity of this asset matters.
Availability Requirement (AR) How much the availability of this asset matters.
06Modified base metrics
Modified Attack Vector (MAV) Value in your environment, if it differs from the base metric.
Modified Attack Complexity (MAC) Value in your environment, if it differs from the base metric.
Modified Attack Requirements (MAT) Value in your environment, if it differs from the base metric.
Modified Privileges Required (MPR) Value in your environment, if it differs from the base metric.
Modified User Interaction (MUI) Value in your environment, if it differs from the base metric.
Modified Confidentiality (MVC) Value in your environment, if it differs from the base metric.
Modified Integrity (MVI) Value in your environment, if it differs from the base metric.
Modified Availability (MVA) Value in your environment, if it differs from the base metric.
Modified Confidentiality (MSC) Value in your environment, if it differs from the base metric.
Modified Integrity (MSI) Value in your environment, if it differs from the base metric.
Modified Availability (MSA) Value in your environment, if it differs from the base metric.
07Supplemental metrics (no effect on the score)
Safety (S) Risk to the physical safety of people (IEC 61508).
Automatable (AU) Can the attack steps be automated across many targets?
Recovery (R) How the system recovers after the attack.
Value Density (V) Resources gained from a single exploitation.
Response Effort (RE) Effort needed to fix or mitigate.
Provider Urgency (U) Rating published by the provider (the standard’s colour codes).

What is CVSS?

CVSS, the Common Vulnerability Scoring System, is a vulnerability severity scoring system maintained by FIRST. A vector records the selected metrics and is used to calculate a score from 0 to 10. That score alone does not measure an organisation’s risk.

CVSS 4.0 and CVSS 3.1

The Common Vulnerability Scoring System, maintained by FIRST, rates a vulnerability from 0 to 10. FIRST published CVSS 4.0 in November 2023: it is the current version and opens by default. CVSS 3.1 is still common in CVE records, scanners and audit reports, hence the second tab. Paste a vector into “Load a vector” and the tool switches to the right version; a 3.0 vector is rescored as 3.1.

What changes in 4.0

CVSS 4.0 adds Attack Requirements (AT), which separate deployment conditions from Attack Complexity (AC). User Interaction distinguishes a passive victim from an active one. Scope (S) is gone: impact is rated separately on the vulnerable system (VC, VI, VA) and on subsequent systems (SC, SI, SA). The temporal group becomes “threat”, reduced to Exploit Maturity (E). Supplemental metrics (Safety, Automatable, Recovery and others) describe the flaw without changing the score.

The scoring changes too. The vector is placed in one of 270 MacroVectors, equivalence groups whose scores FIRST set with experts, then adjusted for the distance to the most severe vector of the group. Quote a 4.0 score with its nomenclature: CVSS-B for base only, CVSS-BT with threat, CVSS-BE with environmental, CVSS-BTE with both.

Exploitability

Attack Vector (AV) is Network when the flaw can be exploited remotely, including from the internet. Adjacent covers the same network segment, Bluetooth or Wi-Fi. Local assumes a session or a file opened on the machine, and Physical requires hardware access. Privileges Required (PR) and User Interaction (UI) say whether an account is needed and whether a victim has to act.

CVSS 3.1: scope, temporal, environmental

In 3.1, Scope (S) is Changed when exploitation reaches resources outside the authority of the vulnerable component, for example a container escape or an XSS that runs in the victim’s browser. Temporal metrics (exploit code maturity, remediation level, report confidence) can only lower the score. Environmental metrics weight the impact by the importance of the asset and let you redefine each base metric for your system.

The limits of the score

A CVSS score does not measure risk. A 9.8 on an isolated server can be less urgent than a 6.5 under active exploitation on your VPN gateway. Cross-check the score with known exploitation (CISA KEV), exploitation probability (EPSS) and the actual exposure of the asset.

A vendor’s published score reflects the reasonable worst case. Recompute it for your configuration rather than copying it, and record your choices: the vector is what makes the score verifiable.

Scoring engine

Scores are computed by the ae-cvss-calculator library by {metæffekt} (Apache-2.0), which implements the FIRST 3.1 and 4.0 specifications. Our tests check its output against reference vectors scored with the code of FIRST’s official calculator.

?Frequently asked questions

Which version should I use, CVSS 4.0 or 3.1?

CVSS 4.0, published by FIRST in November 2023, is the current version and the default tab. Many CVE databases, scanners and reports still show 3.1 scores: the 3.1 tab lets you check or recompute them. Paste a vector and the tool picks the right version.

Does a CVSS score measure risk?

The base score measures the technical severity of a vulnerability, regardless of your context. Risk also depends on actual exposure, the value of the asset, active exploitation (CISA KEV catalogue, EPSS score) and compensating controls. Threat and environmental metrics bring the score closer to your situation.

Why does an unauthenticated RCE score 9.3 in 4.0 and 9.8 in 3.1?

The two versions compute differently. In 3.1, a formula combines impact and exploitability: with an unchanged scope, the maximum is 9.8. In 4.0, the vector is placed in a MacroVector whose score was set by experts, then adjusted: with no impact on subsequent systems (SC, SI, SA at N), the result is 9.3.

What do CVSS-B, CVSS-BT, CVSS-BE and CVSS-BTE mean?

This is the CVSS 4.0 nomenclature: B for base metrics only, T when exploit maturity is set, E when environmental metrics are set. Always quote a score with its nomenclature, because 8.1 as CVSS-BT and 9.3 as CVSS-B can describe the same flaw.

How is the score computed?

The scoring uses the ae-cvss-calculator library by {metæffekt} (Apache-2.0 licence), which implements the FIRST 3.1 and 4.0 specifications. Our unit tests compare its output with reference vectors scored by the code of FIRST’s official calculator.

Are my vectors sent anywhere?

Everything runs in your browser. The vector is written to the URL fragment (#CVSS:4.0/… or #CVSS:3.1/…) so that you can share the link, and browsers never send the fragment to the server.

+More tools

Technical assessment

Request an application or infrastructure assessment

For an assessment by our team, specify the systems involved, available access and requested tests in your enquiry.