feat(cve5): support WordPress ecosystem extraction - #5832
Draft
jess-lowe wants to merge 9 commits into
Draft
Conversation
G-Rath
approved these changes
Aug 12, 2026
G-Rath
left a comment
Collaborator
There was a problem hiding this comment.
ooohhh I just realized I'll need to figure out how WordPress versions work for semantic 🫠
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds support for extracting and converting WordPress vulnerability data (Core, Plugins, Themes) from CVE5 records, with tailored handling for Wordfence, Patchstack, and WPScan CNAs.
Changes
Rationale
WordPress records often rely on SVN or custom CNA identifiers rather than standard Git commits. This change enables high-fidelity ingestion of WordPress-specific data while retaining linkage to Git history where possible, ensuring comprehensive coverage for WordPress users.