Understanding Vulnerabilities Issues

The Vulnerabilities Issues page lists all vulnerabilities currently identified by Selki across your monitored systems.

It complements the Analytics page by providing a detailed, issue‑by‑issue view so you can investigate and remediate specific problems. You can filter issues by status or risk level, search for particular hosts or vulnerabilities, and drill into each issue for background information and remediation guidance.

Understanding the list view

Vulnerability Issues displays a two‑panel layout: a filter panel on the left and an issue table on the right.

Filter panel

• Status filters – The left panel shows counts of issues by status: Open, Investigating, Resolved, Risk Accepted, and False Positive. The counts allow you to gauge workload and filter the list to a particular stage.
• Risk level filters – You can also filter by severity: Critical, High, Medium, Low, or Info. Clicking a severity shows only issues of that level.

Issue table

The main table lists individual vulnerabilities with columns for quick triagedashboard.selki.io:

Working with issues

Opening an issue

Click any row to open the issue details. Each issue page contains two tabs — Overview and Findings. Use the back arrow to return to the list.

Risk Assessment

At the top of the Overview tab is a Risk Assessment panel. It summarises the severity of the vulnerability:

• CVSS score and risk level – A large number (e.g., 9.8/10) accompanied by labels like Critical or High.
• Base metrics – The CVSS v4 vector components (Attack Vector, Attack Complexity, Privileges Required, User Interaction, Scope, Confidentiality, Integrity, Availability) are displayed with coloured badges.
• Additional metrics – Metrics such as EPSS (exploit prediction score), QoD (detection quality), Blast Radius (percentage of the organization potentially affected), and percentage of Assets at risk give more context.

Vulnerability Intelligence

A panel on the right provides metadata:

• First detected / Last detected timestamps.
• Source database (e.g., OWASP ZAP) and the current status (Active).
• Assignee field to assign remediation ownership.
• A Request Mitigation button allows you to formally request mitigation from administrators.

Summary and technical explanation

The Summary section describes what the vulnerability is, how attackers exploit it and why it matters. For example:

• An SQL Injection issue summary notes that attackers can interfere with queries and potentially access or manipulate data; it explains how malicious code is injected and why it leads to data breach risks.
• A Vulnerable JS Library issue summary points out that outdated libraries enable cross‑site scripting or other injection attacks, letting attackers execute arbitrary code or steal data.

The How It Works subsection uses bullet points to explain common exploit techniques, such as unsanitised input in SQL queries or insecure JavaScript functions that execute user‑provided code. Why It Matters lists the business impacts—data breaches, unauthorized access, compliance violations and reputational damage. Technical Details provide deeper context (e.g., vulnerable code patterns).

Solution guidance

The Solution tab outlines actionable remediation steps. These are organized into sections such as Immediate Steps, Best Practices, Secure Coding Practices and Long‑term Remediation. In the example issue in the screenshot above:

• For SQL Injection: enforce strict input validation and use parameterized queries instead of string concatenation. Best practices include escaping user inputs, limiting database privileges and conducting regular security audits. Long‑term remediation suggests using ORM frameworks and providing developer security training.
• For a vulnerable JS library: immediately disable unsafe functions and implement input validation, regularly update libraries, enable a Content Security Policy, avoid eval() and sanitize inputs, and establish a library management process.

These sections provide practical guidance for development teams to fix the vulnerability.

References and Internal Notes

The right panel includes References—CVE identifiers, CWE categories and external links to trusted resources (e.g., OWASP cheat sheets)dashboard.selki.io. An Internal Notes section allows team members to record observations or remediation plans within Selki.

Findings tab

The Findings tab lists each individual instance of the vulnerability across your environment. A summary banner shows counts of findings (total, open, investigating, risk‑accepted, resolved)dashboard.selki.io. Below it, a table lists each asset with columns for status, hostname, port, protocol, description, first seen, last seen and scanner. This helps security teams determine which hosts are affected and track resolution progress.

Tips for using the Issues page

• Prioritise by severity – Use the risk filters and CVSS scores to focus on critical and high‑severity issues first.
• Leverage search and filters – Narrow the list by host name, IP or description to find relevant issues quickly.
• Assign ownership – Click the assignee field on each issue to delegate remediation and ensure accountability.
• Review risk assessment metrics – EPSS, QoD and Blast Radius help estimate exploitation likelihood and organisational impact.
• Follow remediation guidance – The Solution tab provides step‑by‑step recommendations and secure coding practices.
• Track progress in Findings – Mark findings as investigating or resolved, and use the tab to verify that vulnerabilities no longer appear during scans.

By understanding the structure and features of the Vulnerabilities Issues, you can efficiently triage, prioritise and remediate security issues uncovered by Selki. If you would like an in-depth analysis into your attack surface, reach out to Selki today and we'll provide you with a free simple report so you can view what vulnerabilities exist in your organization.

Updated on: 15/09/2025