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.

For CVE-2024-28000, GitHub has an unknown structured affected range but its description states 1.9 through 6.3.0.1. Patchstack states affected versions up to 6.3.0.1 and historical fix 6.4. This is not a current-version recommendation.
Historical record comparison checked 17 October 2026. An empty structured field does not erase the affected range in an advisory description. Version 6.4 is the fix for this issue, not a current-version recommendation. Awesome Websites; original explanatory graphic · Original site graphic Enlarge image

Know what each source contributes

SourceUseful roleWhat to inspect in your example
CVE ProgramIdentifiers and CVE Records published through its numbering authoritiesRecord status, assigning authority and references
NVDAnalysis and enrichment of vulnerability recordsAnalysis status and source of each score
GitHub Advisory DatabaseReviewed and unreviewed advisories; structured package fields can be incompleteReview status, affected package, version range and references
OSVA common vulnerability schema and ecosystem queriesEcosystem, package identity, ranges and aliases
EPSSAn estimate of exploitation probability over the next 30 daysScore 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.

FieldGitHub advisoryPatchstack record
IdentifierCVE-2024-28000 / GHSA-3cp9-7899-h8r7CVE-2024-28000
PackageNo structured package listed; description names LiteSpeed CacheWordPress plugin litespeed-cache
Affected rangeStructured field unknown; description says 1.9 through 6.3.0.1Lists versions through 6.3.0.1
FixStructured patched-version field unknown6.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:

ItemReport valueUpstream valueResolution
Package identityFill from reportFill from advisoryMatch or investigate
Installed versionFill from inventoryNot an advisory fieldRecord how obtained
Affected rangeFill from reportCopy range and its sourceExplain any disagreement
Fixed versionFill if givenFill if explicitly documentedDo not infer from a release date
Status and dateRecord scan timeRecord advisory update timeRecheck 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.