wpscanteam / wpscan

WPScan WordPress security scanner. Written for security professionals and blog maintainers to test the security of their WordPress websites. Contact us via contact@wpscan.com
https://wpscan.com/wordpress-cli-scanner
Other
8.49k stars 1.25k forks source link

New feature: list wp plugin url by each found plugin #299

Closed pvdl closed 10 years ago

pvdl commented 10 years ago

Current output: | Name: fancy-cool-wp-plugin | Location: http://www.example.com/wp-content/plugins/fancy-cool-wp-plugin/ | Readme: http://www.example.com/wp-content/plugins/fancy-cool-wp-plugin.txt

Desired output: | Name: fancy-cool-wp-plugin | Location: http://www.example.com/wp-content/plugins/fancy-cool-wp-plugin/ | Readme: http://www.example.com/wp-content/plugins/fancy-cool-wp-plugin.txt | Info: https://wordpress.org/plugins/fancy-cool-wp-plugin/

The reason is to check quick the latest status of a found plugin. It saves me some 'copy-paste' actions.

A better place for 'Info' is straight after 'Name'

fgeek commented 10 years ago

Good idea and needed feature in my opinion. SCM URL might be too much for regular users :+1:

firefart commented 10 years ago

hm...I implemented this in the "old version". Maybe @erwanlr knows where it is gone :D

fgeek commented 10 years ago

To bit heaven.

erwanlr commented 10 years ago

To Hell ! :P

All plugins are not from WP, like Premium / Private ones. Meaning we would have to check if it's a WP plugin or not (and if it's not, get the correct vendor url ?), furthermore, some of them have been disabled by WP so the url would lead to a 404. So, too much trouble for so little at this time

pvdl commented 10 years ago

Maybe an extra optional info URL tag in the XML file will solve this conflict. Result: wordpress --- vulnerability ------title ------info - The new tag!!! ------references ---------cve

fgeek commented 10 years ago

Tag "info" is not self-explanatory and you can already add URLs as references.

ethicalhack3r commented 10 years ago

Closing