Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/reporting-cvss-scoringReporting and compliance

reporting-cvss-scoring

⁨Assign a defensible severity to a finding — build the CVSS 3.1 vector from demonstrated impact and reconcile it with the program's own scale. Load on "what severity", "CVSS", "rate this bug", or before submitting a report. Signals: a confirmed finding needing a score, a program VRT/severity policy, ⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/reporting-cvss-scoring

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
gBB/++i/xm…H4+b9pAA==The CLI checks the SHA-256 and the signature before it writes a file.
Package0c5fb627…3e4d237a
0c5fb62703c3…3ecc3e4d237a1 file · ⁦1.5 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/reporting/reporting-cvss-scoring@ee0e0c5

When it applies

A finding is reproduced and you must put a number on it — for a report, a dispute, or triage. A defensible score gets paid/prioritised fairly; an inflated one gets you closed as N/A and hurts your credibility.

Why it works

CVSS decomposes severity into metrics you justify one at a time from what you proved, not what's theoretically possible. Grounding each metric in demonstrated impact makes the score arguable and consistent, and mapping it to the program's scale turns it into the right payout/priority.

Method

  1. Score from demonstrated impact, metric by metric (CVSS 3.1 Base):
    • AV (Attack Vector): Network for a remote web bug, down to Physical.
    • AC/PR/UI: was it reliable (low complexity)? did it need auth (privileges)? did it need a victim action (user interaction)? Set from what your PoC actually required.
    • S (Scope): Changed if the bug crosses a trust/authority boundary (e.g. SSRF into internal services, sandbox escape) — a big multiplier, so justify it.
    • C/I/A: rate confidentiality/integrity/availability from what you demonstrated, not the worst imaginable.
  2. Produce the vector + score with the FIRST calculator (e.g. AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
  3. Reconcile with the program: map to Bugcrowd's VRT or the program's severity matrix — the program's policy is the ruling, CVSS is the starting point (tradecraft-bugbounty-platforms).
  4. Write the one-line justification for any contested metric (usually Scope and PR).

Gotchas

  • Don't claim Critical for a self-XSS, a bug needing implausible preconditions, or theoretical impact you didn't show — inflation gets you downgraded and distrusted.
  • Scope:Changed is the most abused metric — only when a real authority boundary is crossed.
  • A chain can score higher than any single bug; score the demonstrated chain (exploit-chaining).
  • CVSS ignores business context; the program's own scale (or a pentest's risk rating) may override.

Verify success

You have a CVSS vector whose every metric you can defend from your PoC, plus the program-scale severity it maps to — and it survives a sceptical triager.

References

FIRST CVSS 3.1 specification & calculator; Bugcrowd VRT; program severity policies.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c50c5fb627Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login