In today's world, data breaches and cyberattacks are very common. There are many news reports of the latest cyber incident nearly every week. You can understand why cybersecurity is an increasing concern for businesses with lots of data breaches happening all around the world.

The primary security measure to prevent cyber attacks is software patching. Many organizations know the benefits of patching, but the challenge begins when carrying out patching as a routine activity.  

As stewards of the lush and vast landscape of security vulnerabilities, we felt obliged to share with you the top trending CVEs of the past month (who's excited for winter to be over?! 😁☀️🌷). Brace yourself! Ok, here we go.

As stewards of the lush and vast landscape of security vulnerabilities, we felt obliged to share with you the top trending CVEs of the past month (who's excited for winter to be over?! 😁☀️🌷). Brace yourself! Ok, here we go.

An Overview of CVSS Score

The Common Vulnerability Scoring System (CVSS) is the industry standard for scoring the severity of a vulnerability. In this article, we will take a closer look at this score. 

The Common Vulnerability Scoring System (CVSS) offers a way to capture the major features of a vulnerability and produce a numerical score showcasing its severity. The numerical score can then be translated into a qualitative representation such as low, medium, high and critical to assist companies to effectively assess and prioritize their vulnerability management processes.

The Common Vulnerability Scoring System (CVSS) offers a way for companies to assess the fundamental features of a vulnerability and produce a numerical score showcasing its severity. The CVSS has proven to be beneficial to assess vulnerabilities and to standardize security policies. But, it has also shown some inadequacies in addressing the needs of users outside of traditional IT environments. 

Common Vulnerability Scoring System (SVSS) version 3.0 framework was the last one that was published by the organization responsible for creating it. It was created by the Forum of Incident Response and Security Teams (FIRST).