MetaCyberGuruPractical tools. Clear explanations.

Security & Privacy / BROWSER-ONLY UTILITY

CVSS v3.1 Base Calculator

Choose the eight Base metrics from your evidence and calculate the CVSS v3.1 score. The calculator handles the arithmetic, not the decision about whether a vulnerability exists or its business impact.

Local processingNo account or AI required

Choose a value for each of the eight metrics, or import an existing v3.1 Base vector. Temporal, Environmental and v4.0 metrics are not supported. Limit: 100,000 characters.

Loading local tool code...

Input stays in this tab. No upload, AI call, analytics or ads. Reset clears the workspace. Clipboard copies and downloaded files remain under your control.

Eight choices, no inferred answers

Choose Attack Vector, Attack Complexity, Privileges Required, User Interaction, Scope, Confidentiality, Integrity and Availability. The form builds the standard vector from those choices. If you already have a v3.1 Base vector, import it instead and review the populated selections. Missing or repeated metrics and unsupported groups are rejected rather than assigned a score.

Rounding is part of the calculation

The calculation follows the v3.1 Base equations, including the changed-Scope privileges weights. It uses the integer Roundup procedure in FIRST Appendix A to avoid an extra tenth caused by floating-point noise. It does not calculate Temporal or Environmental scores, and it must not be labelled CVSS v4.0.

A severity label is not business risk

The sample produces a 9.8 Critical Base score for the metrics supplied. That label describes the CVSS severity band. Asset importance, actual exposure and compensating controls still need separate consideration. The tool does not look up a CVE, establish exploitation or recommend an incident priority.

Record why each value applies

Before sharing a score, explain the attack conditions and the security authority affected by Scope. Revisit assumptions when evidence changes. Copy and download include your vector and calculated values, not a validation of your underlying assessment.

References

Documentation reviewed: . Rule results describe the supplied text, not a live application test.

Useful next steps

Maintained by MetaCyberGuru. A review point may need source, runtime or deployment context before you act on it.