APIv2 integration

[ethicalhack3r]

Any volunteers for implementing APIv2 into WPScan v2.x? @erwanlr @firefart

Would fix #704
Maybe fix #514

If no volunteers I can do it :)

New structure for those unaware:

{
  "name": "zedity",
  "latest_version": "6.2.0",
  "last_updated": "2015-08-12T21:51:00.000Z",
  "popular": false,
  "vulnerabilities": [
    {
      "id": 7142,
      "title": "Zedity <= 2.5.0 - Cross-Site Scripting (XSS)",
      "created_at": "2014-08-01T10:59:11.000Z",
      "updated_at": "2015-07-04T19:28:53.000Z",
      "published_date": null,
      "references": {
        "url": [
          "http:\/\/www.securityfocus.com\/bid\/65799\/",
          "http:\/\/packetstormsecurity.com\/files\/125402\/"
        ],
        "osvdb": [
          "103789"
        ],
        "secunia": [
          "57026"
        ]
      },
      "vuln_type": "XSS",
      "fixed_in": "2.5.1"
    },
    {
      "id": 7143,
      "title": "Zedity <= 2.4.0 - Cross-Site Scripting (XSS)",
      "created_at": "2014-08-01T10:59:11.000Z",
      "updated_at": "2015-07-04T19:28:37.000Z",
      "published_date": null,
      "references": {
        "url": [
          "http:\/\/packetstormsecurity.com\/files\/125402\/"
        ]
      },
      "vuln_type": "XSS",
      "fixed_in": "2.5.1"
    }
  ]
}

Now incorporates latest_version for the plugin/theme and last_updated for the plugin/theme.

As well as including the popular tag for plugins/themes and including all plugins/themes not just those that have known vulnerabilities. This means we can combine all of our data files into one single file.

Some other data implemented such as vulnerability published_date

[firefart]

can have a look at it once i get the new server up and running. Of and can we rename APIv2 to Fileformat v2 or smth? :)
I think the API is the current /api/ endpoint getting you live data. The json files we use are no API jsons, they are generated once a day so they are static files :)

[ethicalhack3r]

Been doing some work on it just to get a "poc" working so I can create a pull request and ask for some feedback.

Not sure what you mean about the file format? or the api endpoint? :)

[ethicalhack3r]

Still need to:

• implement last_updated and latest_version
• fix specs

[ethicalhack3r]

Just need to:

• implement last_updated and latest_version

[ethicalhack3r]

Any ideas on how to implement implement last_updated and latest_version into the output? :)

[ethicalhack3r]

@erwanlr any chance you could look into implementing latest_version and last_updated when you get some spare time? I'm unsure as to the best way to implement it...

Everything else should be in place

[erwanlr]

Done.

Furthermore, It would be cool to not push any new features to the v2 as specs are a mess given that they are not correctly updated when such features are implemented.

[ethicalhack3r]

Awesome :D

I will fix the popular bug then pull these changes in.

I think you're right about new features for the 2.x branch. Shall we release a final 2.9 version once this is pulled in? then we can do a code freeze on wpscan 2.x?

[ethicalhack3r]

Merged