Help Center

Find answers to common questions about CVE data and our platform

Quick Search Tips

Search by CVE ID: Use the exact format CVE-YYYY-NNNNN (e.g., CVE-2024-1234)

Search by Keyword: Enter vulnerability type or affected software (e.g., "sql injection" or "Apache")

Filter by Severity: Use our filters to show only HIGH or CRITICAL vulnerabilities

Filter by Date: Find vulnerabilities published within a specific time range

Getting Started

What is a CVE?

A CVE (Common Vulnerabilities and Exposures) is a unique identifier assigned to publicly disclosed cybersecurity vulnerabilities. Each CVE provides a reference for a specific vulnerability, allowing security professionals to communicate about threats effectively.

How do I search for a specific CVE?

You can search for a specific CVE using the search bar on our homepage or navigate directly by typing the CVE ID in the URL. For example: /cve/CVE-2024-1234. You can also use our advanced search with filters for severity, date range, and keywords.

Is there a cost to use CVEDatabase.com?

No, our service is completely free. We provide free access to CVE data, search functionality, and analysis tools for all users.

Vulnerability Information

What do CVSS scores mean?

CVSS (Common Vulnerability Scoring System) scores range from 0-10 and indicate the severity of a vulnerability. Learn more in our CVSS Guide. Generally: 0-3.9 (Low), 4.0-6.9 (Medium), 7.0-8.9 (High), 9.0-10.0 (Critical).

What is EPSS and how does it differ from CVSS?

EPSS (Exploit Prediction Scoring System) predicts the likelihood of a vulnerability being exploited, while CVSS measures the severity of impact. Both metrics are valuable for prioritization. See our EPSS Guide for details.

How often is the CVE database updated?

Our database is updated daily with new CVE information from the National Vulnerability Database (NVD). New vulnerabilities are added continuously as they are discovered and disclosed.

Features & Tools

What is the Executive Summary feature?

Our Executive Summary tool provides AI-generated, non-technical summaries of CVE vulnerabilities for stakeholders and leadership. These summaries explain the impact and importance without requiring deep technical knowledge.

How does the Remediation Guide work?

The Remediation Guide provides step-by-step instructions for addressing specific vulnerabilities. It includes patching recommendations, workarounds, and best practices for securing systems against the identified threat.

What is the Bulk Analysis tool?

Bulk Analysis allows you to analyze multiple CVEs at once. Upload a list of CVE IDs to get comprehensive analysis, including trends, severity distribution, and actionable recommendations.

API Integration

Do I need an API key to use the API?

No, our API is public and does not require authentication. However, rate limiting applies to ensure fair usage. See our API Documentation for details.

What are the rate limits for the API?

The API allows 50 requests per minute and 1,000 requests per hour per IP address. Rate limit information is provided in response headers.

What response formats does the API support?

Our API returns responses in JSON format, which is compatible with the National Vulnerability Database (NVD) API schema for seamless integration.

Troubleshooting

Why am I seeing a "CVE not found" error?

CVE IDs follow a specific format: CVE-YYYY-NNNNN. Ensure you are using the correct ID. If the CVE recently was published, there may be a short delay before it appears in our database.

Why is my search returning no results?

Try broadening your search criteria. Make sure your keywords are spelled correctly and relevant to vulnerability descriptions. You can also try searching by date range instead of specific keywords.

What should I do if I find outdated or incorrect information?

Please contact us using our Contact form with details about the issue. We take data accuracy seriously and will investigate and correct any errors.

Privacy & Security

Is my search history stored?

We do not store personally identifiable information or search history. See our Privacy Policy for complete details about data handling.

Is the data on CVEDatabase.com secure?

Yes, we use industry-standard security measures to protect our infrastructure. All data is from official sources (NVD, CISA) and we comply with security best practices.

Can I use this data commercially?

Our data comes from public sources and can be used in most commercial applications. See our Terms of Service for specific licensing and usage rights.

AI-Powered Remediation

Our AI-powered remediation feature provides intelligent, context-aware guidance for addressing vulnerabilities:

  • Smart Patch Recommendations: Get tailored patching strategies based on your specific environment and the vulnerability's characteristics.
  • Step-by-Step Instructions: Receive detailed remediation steps written in clear, actionable language.
  • Workaround Suggestions: When patches aren't immediately available, get temporary mitigation strategies.
  • Risk Context: Understand the real-world implications of each vulnerability with AI-generated summaries.

Access AI remediation by viewing any CVE detail page and clicking the "AI Remediation" button.

Export Options

Export your CVE analysis and reports in multiple formats for easy integration with your workflow:

  • JSON: Machine-readable format perfect for automation, scripting, and integration with security tools.
  • CSV: Spreadsheet-compatible format ideal for Excel, Google Sheets, and data analysis.
  • Markdown: Human-readable format great for documentation, wikis, and technical reports.

Export options are available on CVE detail pages and bulk analysis results.

JIRA Integration

Streamline your vulnerability management workflow with our JIRA-ready export format:

  • One-Click Copy: Copy CVE details formatted specifically for JIRA tickets.
  • Action Items: Pre-formatted task lists with remediation steps ready for assignment.
  • Priority Mapping: Severity levels automatically mapped to JIRA priority fields.
  • Rich Formatting: Tables, headers, and structured content that renders properly in JIRA.

Click the "Copy for JIRA" button on any CVE detail page to get formatted content.

GitHub Issues Integration

Create security issues in your GitHub repositories with pre-formatted vulnerability reports:

  • Markdown Format: Content formatted with GitHub-flavored Markdown for perfect rendering.
  • Issue Templates: Structured format including severity badges, affected components, and remediation steps.
  • Labels Ready: Suggested labels for security, priority, and affected areas.
  • Checklist Tasks: Pre-built task checklists for tracking remediation progress.

Use the "Create GitHub Issue" button on CVE detail pages to generate formatted content.

Important Note

CVE information is provided for informational purposes. Always conduct thorough security assessments and consult with security professionals before taking action on vulnerabilities affecting your systems.