DependencyTrack / DependencyTrack/dependency-track

Add WPScan or Wordfence as analyzer or mirror

Open
#4,598 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Java
Stars
4.2k
Forks
811
Avg merge
8h 39m
Merged PRs (30d)
237

Description

### Current Behavior

Currently Wordpress vulnerabilities are not covered completely by Dependency Tracks sources. If they have a CVE, the probably are detected.
But many plugins have vulnerabilities without a CVE (or GHSA, OSV, SNYK, .... ID).

### Proposed Behavior

Popular sources for Wordpress vullnerabilities are
- [WPScan](https://wpscan.com/api/)
- [Wordfence](https://www.wordfence.com/help/wordfence-intelligence/v2-accessing-and-consuming-the-vulnerability-data-feed/)

The problem with WPScan is that they do not allow any mirroring and do not allow even storing vulnerabilities. Unless you have a commercial enterprise license.

Wordfence seems to have almost the same (20k) vulnerabilities, but is completely free to use including mirroring.

There are some questions to be answered:
- Vulnerabilities (WPScan + Wordfence) have a uuid as ID. This doesn't really look/fit very well in the DT UI;
- Similar to my question in https://github.com/DependencyTrack/dependency-track/pull/4515#issuecomment-2571643008 is whether we should replicate all vulnerabilities as those which have a CVE are just copies of the vulnerability from NVD.

### Checklist

- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this enhancement was already requested

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.