[GHSA-j77f-79w9-rghc] The wp-enable-svg WordPress plugin through 0.7 does not... #5224
Conversation
This file contains 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
github-actions
bot
changed the base branch from
main
to
Rudloff/advisory-improvement-5224
|
Hi @Rudloff, given the discrepancy with the version, we are not confident that mwdelaney/wp-enable-svg is the same as the |
|
I wrote an email to WPScan regarding the version discrepancy and will keep you updated. |
|
The version range in the advisory was updated: https://wpscan.com/vulnerability/fc982bcb-9974-481f-aef4-580ae9edc3c8/ |
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.
Updates
Comments
The CVE does not contain a link to the GitHub source code.
But this reference can be used to confirm the relationship between the WP package and the GitHub repository: https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/wp-enable-svg
(I am not sure the version range of the CVE is correct, the latest release of the plugin is 0.2.)