Base score
The intrinsic severity of the vulnerability, stored for full auditability.
We use analytics and ad-measurement cookies (Google, Meta). Nothing is sold, and you can decline.
Severity alone never told you what to fix. CybeDefend scores every finding and ranks every project by real, exploitable risk, so your team spends its time where it counts.
Hover a signal to see its share of the score.
CVSS 4.0 environmental score, EPSS exploitation probability, exploitability and business context, weighted into a single number.
The queue advances by priority score, not by severity alone.
Next to fix
CWE-8992SQL injection in refund handler
api/refunds.ts:88Reachable from POST /refunds on an internet-facing service.
provenEPSS 0.94Click the top card to advance the queue.
exploitability_statusnot_exploitableFalse positive or unreachable. De-prioritized.theoreticalPossible, not yet confirmed reachable.provenConfirmed exploitable in your real data flow.actively_exploitedKnown exploitation in the wild. Drop everything.Every finding gets a verdict on whether it is realistically reachable, from static analysis, AI review or a manual call.
One CybeRisk score per project, so you know which of a hundred projects to open first.
Both scores start from CVSS 4.0. The same CVE scores higher on an internet-facing, mission-critical service than on an isolated internal tool.
The intrinsic severity of the vulnerability, stored for full auditability.
Reshaped by your Security Context, and recomputed automatically when it changes.
Reshaped by your contextInternet exposure · Network segmentation · Data classification · Business criticality
The documentation walks you through setup, configuration and every option.
Read the docsPlatform Overview / Key Features
Priority Scoring
The 0 to 100 formula and its weights, CVSS 4.0, EPSS, exploitability and context, the levels and manual override.
The priority score ranks individual findings inside a project so you know what to fix first. The CybeRisk score ranks whole projects across your portfolio so you know which project to look at first. One is finding-level, the other project-level.
It blends four normalized signals: CVSS 4.0 environmental score, EPSS exploitation probability, exploitability and business context. The weighted result is a transparent 0 to 100, and every finding can be decomposed into its exact contributions.
It is a verdict on whether a finding is realistically reachable, from not_exploitable to actively_exploited, sourced from static analysis, AI assessment or a manual override. It is the single biggest driver of false-positive suppression.
Because it sums point contributions from every active finding rather than a percentage. A project with many critical vulnerabilities can legitimately score in the hundreds, which keeps the worst offenders clearly separated.
Yes. Authorized users can pin a priority, which freezes recalculation until it is cleared. Overridden findings are flagged so it is always clear a human set the score.
One command wires every coding agent on your machine to CybeDefend: your business rules, your compliance frameworks, and guards that block destructive calls before they fire.
npx -y @cybedefend/vibedefend@latest install