On this page
Compare records, not database counts
A list of eight feeds tells you little about whether a scanner can match a particular plugin and version correctly. Start with one finding from your own report. Write down the plugin slug, installed version, vulnerability identifier and the source cited by the scanner. Then compare that record with the upstream advisory.
This worksheet separates three questions: who identifies the vulnerability, who adds analysis, and which record describes the affected software.

Know what each source contributes
| Source | Useful role | What to inspect in your example |
|---|---|---|
| CVE Program | Identifiers and CVE Records published through its numbering authorities | Record status, assigning authority and references |
| NVD | Analysis and enrichment of vulnerability records | Analysis status and source of each score |
| GitHub Advisory Database | Reviewed and unreviewed advisories; structured package fields can be incomplete | Review status, affected package, version range and references |
| OSV | A common vulnerability schema and ecosystem queries | Ecosystem, package identity, ranges and aliases |
| EPSS | An estimate of exploitation probability over the next 30 days | Score date and the CVE being scored |
These roles come from the CVE Program, NVD overview, GitHub database documentation, OSV documentation, and FIRST's EPSS description. EPSS is a probability estimate, not a substitute for the advisory's affected-version information.
Work through one finding
Here is a historical record comparison checked on 17 October 2026. CVE-2024-28000 concerns the WordPress LiteSpeed Cache plugin. GitHub's GHSA-3cp9-7899-h8r7 entry is unreviewed: its structured package and version fields are unpopulated, although its description gives an affected range. Patchstack's record identifies the fix for this vulnerability.
| Field | GitHub advisory | Patchstack record |
|---|---|---|
| Identifier | CVE-2024-28000 / GHSA-3cp9-7899-h8r7 | CVE-2024-28000 |
| Package | No structured package listed; description names LiteSpeed Cache | WordPress plugin litespeed-cache |
| Affected range | Structured field unknown; description says 1.9 through 6.3.0.1 | Lists versions through 6.3.0.1 |
| Fix | Structured patched-version field unknown | 6.4 for this specific issue |
Sources: GitHub advisory and Patchstack's vulnerability record. This is a comparison of published records, not an observed scanner result. For a hypothetical installed version 6.3.0.1, the stated range includes it. A blank GitHub field does not cancel that evidence. Version 6.4 is the historical fix for this issue, not a recommendation to install an old release today.
Copy the identifier from your report rather than searching only for a plugin's display name. Open the cited advisory and record its URL and retrieval date. Compare the vendor, package ecosystem and version range with the installed software. If the record has aliases, record those alongside the primary identifier so you do not count the same underlying issue twice.
Use this small evidence table:
| Item | Report value | Upstream value | Resolution |
|---|---|---|---|
| Package identity | Fill from report | Fill from advisory | Match or investigate |
| Installed version | Fill from inventory | Not an advisory field | Record how obtained |
| Affected range | Fill from report | Copy range and its source | Explain any disagreement |
| Fixed version | Fill if given | Fill if explicitly documented | Do not infer from a release date |
| Status and date | Record scan time | Record advisory update time | Recheck stale evidence |
An unresolved mismatch stays unresolved in the worksheet. Picking the highest score does not resolve a package mismatch.
Check reuse terms at the dataset level
An API being publicly reachable does not establish permission to redistribute its records. Before building your own feed, record the exact dataset, licence or terms URL, attribution obligations and retrieval date. Check upstream terms for any data an aggregator republishes. Avoid assigning one blanket licence to NVD, OSV and all their upstream records.
For WPSecScan, compare the documented sources with a dated result from the installed tool. Keep feed availability separate from feed freshness and matching accuracy. This article does not claim that every named provider is currently fetched successfully by a particular release.




