Closed J12934 closed 5 years ago
Items' vulnerabilities are always under <item>.vulnerabilities
, so for a plugin: plugins.<slug>.vulnerabilities
and are the ones reported for the detected version (if the version could not be detected, all the vulnerabilities will be listed)
I will remove the unnecessary vulnerabilities
key under plugin/theme's version.
Ah ok, got it.
Thank you for the fast reply! π
Changes are live in docker in case you are using it. Otherwise they will be in the next version of WPScan
Hi π first of all thank you for your hard work on this awesome tool. We really appreciate all the hard work you put into this!
We facing some confusion looking at the JSON output of one particular case and we are not quite sure, if it is a bug or if we miss understand the intended json structure. I posted the json anonymised below.
WpScan identified the Plugin Yoast SEO with version 9.1. It also found a vulnerability for that version. We expected the vulnerability to be listed under the
plugins.[pluginname].version.vulnerabilities
, as this is a vulnerability for the identified version. But it was listed under just under theplugins.[pluginname].vulnerabilities
.To our understanding the
version.vulnerabilities
should include the vulnerabilities for the currently running version while thevulnerability
should include thevulnerabilities
for any version.Did we understand that wrong or is the json mallformed?
Your environment
MacOS Mojave
Steps to reproduce
Soory, can't disclose the url :(
wpscan was started using the following command:
Expected behavior
The vulnerability should appear in the array of the
plugins.[pluginname].version.vulnerabilities
as this affects the active version.Actual behavior
The vulnerability appears in
plugins.[pluginname].vulnerabilities
.Sidenote
Using the cli this looks as expected: