CVE Detection Intelligence

Enter a product and version — get matching CVEs with affected ranges, fixed versions, and evidence.

v1.2

Scan Product Version

Version range matching · severity · fixed version · CPE guess

Format: product version — separated by space, /, or @.
Unchecked → also show possible (keyword-only) matches

How to Detect CVEs for a Product Version

  1. Enter product + version — e.g. wordpress 7.0.2, nginx/1.24.0, or Apache HTTP Server 2.4.57.
  2. Choose search window — how far back to look (30 days up to 5 years). Narrower windows are faster.
  3. Toggle filter — keep Show only version-matched CVEs on for high precision, or turn off to also see keyword-only possibilities.
  4. Click Detect CVE — the tool parses version ranges from each CVE description and compares your version.
  5. Review results — each card shows severity, CVSS, affected range, fixed version, and a CPE guess.
  6. Copy or download — export the result as plain text or structured JSON for reporting.

Frequently Asked Questions

What is a CVE detector?

A CVE detector takes a product name and version (e.g. wordpress 7.0.2) and finds known Common Vulnerabilities and Exposures (CVEs) that affect that specific version. Unlike a keyword search, it parses version ranges from CVE advisories and only returns entries where your version falls inside the affected window.

How does version matching work?

The tool parses structured statements from each CVE description — patterns like "X through Y", "before X", "X and earlier", or "from X before Y". Your version is compared against each range using semantic version comparison. Results are marked as Version match (exact) or Possible (keyword only, range not parseable).

How accurate is the version matching?

Accuracy depends on how clearly the vendor writes the advisory. Well-written CVEs (WordPress, Apache, GitLab, Cisco) parse correctly in most cases. Some entries don't disclose affected ranges and are marked Possible — always verify against the vendor advisory before acting.

Where does the CVE data come from?

CVE data is aggregated from the National Vulnerability Database (NVD), a public-domain repository maintained by NIST, and enriched by dbcve.org. Severity scores, CVSS vectors, KEV flags, and mitigation notes are added. Results are refreshed continuously and cached for performance.

What does the CPE guess mean?

CPE (Common Platform Enumeration) is a standardized naming scheme for software. The tool constructs an approximate CPE from your product and version, e.g. cpe:2.3:a:wordpress:wordpress:7.0.2:*:*:*:*:*:*:*. Use it as a reference — the official CPE for a given product may use a different vendor/product token.

Is this CVE detector free and safe?

Yes — 100% free, no registration, no data stored. Your input is used only to retrieve matching CVEs and is discarded immediately after the response.

Precise Detection

Version matching filters out CVEs that don't affect your specific build. Every result card shows the parsed range so you can verify the logic.

Live Data

Vulnerability data refreshed continuously with 1-hour cache. Base data derived from the National Vulnerability Database (NVD), enriched by dbcve.org with KEV flags and mitigation notes.

Responsible Use

Use this tool only on assets you own or are authorized to test. Always verify findings against the vendor advisory before acting.

CVE data aggregated from the National Vulnerability Database (NVD, public domain) and enriched by dbcve.org.