🧨CVE Database

The CVE Database in Menaxa offers a powerful way to explore, filter, and act on publicly disclosed vulnerabilities — across two decades of Common Vulnerabilities and Exposures (CVEs), from 2002 to 2025.

Whether you’re a developer trying to secure your stack or a security engineer responsible for patching, this database gives you clarity, speed, and trusted sources.

---

🔍 Overview

Metric	Description
Total CVEs	All known vulnerabilities indexed from 2002–2025 (updated daily)
Critical	Must-fix issues, often actively exploited or unpatched
High Severity	Dangerous vulnerabilities that require attention
Medium Severity	Relevant but often require specific conditions to exploit
Low Severity	Low-risk or low-impact vulnerabilities

---

📂 Severity Classifications

Severity	Color	Meaning
🟥 Critical	Red	Requires immediate patching. Often allows full compromise or RCE.
🟧 High	Orange	Significant risk. May require some conditions to exploit.
🟨 Medium	Yellow	Moderate issues that may affect stability, privacy, or integrity.
🟩 Low	Green	Low-likelihood or low-impact bugs (e.g., DoS, info disclosure).

You can filter CVEs by severity level using the toggle on the top-right of the table.

---

🗃️ CVE Records Table

Column	Description
CVE ID	Unique vulnerability ID (e.g., CVE-2025-4558) — clickable link
Published	Date the CVE was made public
Severity	Risk classification (Critical, High, Medium, Low)
Score	CVSS base score (0.0–10.0) representing exploitability and impact
Description	Summary of the vulnerability, including affected systems and impact

✅ Clicking on a CVE ID will redirect you to its official publishing page (e.g., NVD, GitHub Security Advisories, or vendor-specific pages).

---

📆 Time Range Coverage

You can filter CVEs across multiple years, going all the way back to 2002.

Use this to:

• Audit historical vulnerabilities by vendor, category, or CVSS

• Investigate old-but-still-exploited software

• Track progress in patching trends across time

---

🧠 Use Cases

Role	Use Case
Developers	Check if a dependency has been compromised
Security Engineers	Integrate high/critical CVEs into patch and alert pipelines
Analysts	Investigate which CVEs tie into recent threats
Product Managers	Ensure you’re not shipping vulnerable versions of key components