Consider Author
field for wordpress plugins when generating CPEs
#2946
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Found some examples in the wild where the
Author
field (not just theAuthorURI
field) is useful when extracting potential vendors during CPE generation (see the code diff for the example). This means that there will generally be more CPEs for all wordpress plugins found, but this seems unavoidable as there is non guidance around populating these fields for wordpress (nor for providing CPEs for this ecosystem in NVD).Additionally, this encodes
wordpress
as the target software, as several of the CVEs I've found correctly encode this, and wordpress plugins tend to be a bountiful source of false positives when searching by CPE.