CVSS Exploit Maturity values: Attacked, POC, Unreported, Not Defined
What the four CVSS 4.0 Exploit Maturity values mean, who is supposed to set them, why Not Defined means worst case, and where to get the data.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
What the four CVSS 4.0 Exploit Maturity values mean, who is supposed to set them, why Not Defined means worst case, and where to get the data.
CVSS v4.0 labels each score by the metric groups behind it. Learn what B, BT, BE and BTE mean and why most scores you see are base only, not risk.
CVSS 4.0 replaced Scope with vulnerable and subsequent systems. Learn the boundary rule, with XSS and SQL injection examples from the FIRST FAQ.
CVSS 4.0 splits User Interaction into passive and active. See how FIRST scores clicking a link, reflected XSS, stored XSS and CSRF, and why it matters.
CVSS 4.0 supplemental metrics such as Safety, Automatable, Recovery and Provider Urgency never change the score. Here is what each one tells you.
How to use CVSS 4.0 Environmental metrics: security requirements, modified base metrics, and real examples for isolated hosts, firewalls and safety systems.
CVSS 4.0 split Attack Complexity into two metrics. See how built-in challenges differ from external conditions, with examples and common scoring mistakes.
Seen a scary CVE headline? Run a five step check on exposure, preconditions, exploitation and fix before you page anyone. Includes a demo of the decision.
Coordinated vulnerability disclosure has five roles. What each one owns, where handoffs fail, and what you should do when you are the deployer.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.