Name of Your Organization:

WPScan

Web Site:

http://www.wpscan.org

Adopting Capability:

WPScan Vulnerability Database

Capability home page:

https://wpvulndb.com

General Capability Questions

Product Accessibility <CR_2.4>

Provide a short description of how and where your capability is made available to your customers and the public (required):

WPScan Vulnerability Database is a website that can be accessed from https://wpvulndb.com. Commercial use of our database requires a commercial license.
Mapping Questions

Map Content Selection Criteria <CR_5.4>

Describe the criteria used for determining the relevance of a given CVE Identifier to your Capability (required):

We do not currently use any CVE content apart from the CVE number which is used to link to the NVD.

Map Currency Update Mechanism <CR_5.4>

Describe the mechanism used for reviewing CVE for content changes (required):

We do not currently use any CVE content apart from the CVE number which is used to link to the NVD.

Map Content Source <CR_5.5>

Describe the source of your CVE content (required):

Public advisories released by independent researchers or direct submissions to our website from independent researchers.
Documentation Questions

CVE and Compatibility Documentation<CR_4.1>

Provide a copy, or directions to its location, of where your documentation describes CVE and CVE compatibility for your customers (required):

https://wpvulndb.com/about

Documentation of Finding Elements Using CVE Names <CR_4.2>

Provide a copy, or directions to its location, of where your documentation describes the specific details of how your customers can use CVE names to find the individual security elements within your capability’s repository (required):

https://wpvulndb.com/about

Documentation of Finding CVE Names Using Elements <CR_4.3>

Provide a copy, or directions to its location, of where your documentation describes the process a user would follow to find the CVE names associated with individual security elements within your capability’s repository (required):

https://wpvulndb.com/about

Documentation Indexing of CVE-Related Material <CR_4.4>

If your documentation includes an index, provide a copy of the items and resources that you have listed under "CVE" in your index. Alternately, provide directions to where these "CVE" items are posted on your web site (recommended):

No index currently available.

Type-Specific Capability Questions

Tool Questions

Finding Tasks Using CVE Names <CR_A.2.1>

Give detailed examples and explanations of how a user can locate tasks in the tool by looking for their associated CVE name (required):

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

Finding CVE Names Using Elements in Reports <CR_A.2.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the tool allows the user to determine the associated CVE names for the individual security elements in the report (required):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

Getting a List of CVE Names Associated with Tasks <CR_A.2.4>

Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the tool’s tasks (recommended):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

Selecting Tasks with a List of CVE Names <CR_A.2.5>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):

Users can not provide a file of CVE names.

Selecting Tasks Using Individual CVE Names <CR_A.2.6>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the tool by using individual CVE names (recommended):

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

Non-Support Notification for a Requested CVE Name <CR_A.2.7>

Provide a description of how the tool notifies the user that task associated to a selected CVE name cannot be performed (recommended):

If a vulnerability page cannot display the appropriate HTTP, status code is displayed.
Service Questions

Service Coverage Determination Using CVE Names <CR_A.3.1>

Give detailed examples and explanations of the different ways that a user can use CVE names to find out which security elements are tested or detected by the service (i.e. by asking, by providing a list, by examining a coverage map, or by some other mechanism) (required):

Search

Step 1:
Use the site's search functionality to search for a CVE number. https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

Browsing WordPress versions, Plugin names, or Theme names:

https://wpvulndb.com/wordpresses
https://wpvulndb.com/plugins
https://wpvulndb.com/themes

Finding CVE Names in Service Reports Using Elements <CR_A.3.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the user can determine the associated CVE names for the individual security elements in the report (required):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

Service’s Product Utilization Details <CR_A.3.4>

Please provide the name and version number of any product that the service allows users to have direct access to if that product identifies security elements (recommended):

WPScan version 2.5.1 and above.
Online Capability Questions

Finding Online Capability Tasks Using CVE Names <CR_A.4.1>

Give detailed examples and explanations of how a "find" or "search" function is available to the user to locate tasks in the online capability by looking for their associated CVE name or through an online mapping that links each element of the capability with its associated CVE name(s) (required):

Step 1:
Use the site's search functionality to search for a CVE number. https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

Online Capability Interface Template Usage <CR_A.4.1.1>

Provide a detailed description of how someone can use your "URL template" to interface to your capability’s search function (recommended):

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Online Capability CGI GET Method Support <CR_A.4.1.2>

If the URL template is for a CGI program, does it support the HTTP "GET" method? (recommended):

N/A

Finding CVE Names Using Online Capability Elements <CR_A.4.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the online capability allows the user to determine the associated CVE names for the individual security elements in the report. (required):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

Online Capability Element to CVE Name Mapping <CR_A.4.3>

If details for individual security elements are not provided, give examples and explanations of how a user can obtain a mapping that links each element with its associated CVE name(s), otherwise enter N/A (required):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697
Aggregation Capability Questions

Finding Elements Using CVE Names <CR_A.5.1>

Give detailed examples and explanations of how a user can find associated elements in the capability by looking for their associated CVE name (required):

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

Finding CVE Names Using Elements in Reports <CR_A.5.2>

Give detailed examples and explanations of how, for reports that identify individual security elements, the capability allows the user to determine the associated CVE names for the individual security elements in the report (required):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

Getting a List of CVE Names Associated with Tasks <CR_A.5.4>

Give detailed examples and explanations of how a user can obtain a listing of all of the CVE names that are associated with the capability’s tasks (recommended):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

Selecting Tasks with a List of CVE Names <CR_A.5.5>

Describe the steps and format that a user would use to select a set of tasks by providing a file with a list of CVE names (recommended):

Users are not able to provide a list of CVE names.

Selecting Tasks Using Individual CVE Names <CR_A.5.6>

Describe the steps that a user would follow to browse, select, and deselect a set of tasks for the capability by using individual CVE names (recommended):

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697
Media Questions

Electronic Document Format Info <CR_B.3.1>

Provide details about the different electronic document formats that you provide and describe how they can be searched for specific CVE-related text (required):

HTML

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

JSON

Step 1:
Click on the WordPress version, Plugin or Theme name.

Example: https://wpvulndb.com/wordpresses/40

Step 2:
Click on the API hyperlink.

Example: https://wpvulndb.com/api/v1/wordpresses/40

Electronic Document Listing of CVE Names <CR_B.3.2>

If one of the capability’s standard electronic documents only lists security elements by their short names or titles provide example documents that demonstrate how the associated CVE names are listed for each individual security element (required):

Truncated vulnerability titles may appear on the following pages:

https://wpvulndb.com/
https://wpvulndb.com/wordpresses
https://wpvulndb.com/plugins
https://wpvulndb.com/themes

To view the non-truncated vulnerability title along with the CVE number, the user must click on an individual vulnerability page.

Example:

https://wpvulndb.com/wordpresses/40

Electronic Document Element to CVE Name Mapping <CR_B.3.3>

Provide example documents that demonstrate the mapping from the capability’s individual elements to the respective CVE name(s) (recommended):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697
Graphical User Interface (GUI)

Finding Elements Using CVE Names Through the GUI <CR_B.4.1>

Give detailed examples and explanations of how the GUI provides a "find" or "search" function for the user to identify your capability’s elements by looking for their associated CVE name(s) (required):

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

GUI Element to CVE Name Mapping <CR_B.4.2>

Briefly describe how the associated CVE names are listed for the individual security elements or discuss how the user can use the mapping between CVE entries and the capability’s elements, also describe the format of the mapping (required):

CVE numbers are displayed on the individual vulnerability's page. These link to the NVD.

Example: https://wpvulndb.com/vulnerabilities/7697

GUI Export Electronic Document Format Info <CR_B.4.3>

Provide details about the different electronic document formats that you provide for exporting or accessing CVE-related data and describe how they can be searched for specific CVE-related text (recommended):

HTML

Step 1:
Use the site's search functionality to search for a CVE number.

https://wpvulndb.com/search?utf8=%E2%9C%93&text=CVE-2014-9032

Step 2:
Click on any search results which will appear if the CVE number matches any of the vulnerabilities within our database.

https://wpvulndb.com/vulnerabilities/7697

JSON

Step 1:
Click on the WordPress version, Plugin or Theme name.

Example: https://wpvulndb.com/wordpresses/40

Step 2:
Click on the API hyperlink.

Example: https://wpvulndb.com/api/v1/wordpresses/40
Questions for Signature

Statement of Compatibility <CR_2.7>

Have an authorized individual sign and date the following Compatibility Statement (required):

"As an authorized representative of my organization I agree that we will abide by all of the mandatory CVE Compatibility Requirements as well as all of the additional mandatory CVE Compatibility Requirements that are appropriate for our specific type of capability."

Name: Ryan Dewhurst

Title: Founder/Developer

Statement of Accuracy <CR_3.4>

Have an authorized individual sign and date the following accuracy Statement (recommended):

"As an authorized representative of my organization and to the best of my knowledge, there are no errors in the mapping between our capability’s Repository and the CVE entries our capability identifies."

Name: Ryan Dewhurst

Title: Founder/Developer

Statement on False-Positives and False-Negatives <CR_A.2.8 and/or CR_A.3.5>

FOR TOOLS ONLY - Have an authorized individual sign and date the following statement about your tools efficiency in identification of security elements (required):

"As an authorized representative of my organization and to the best of my knowledge, normally when our capability reports a specific security element, it is generally correct and normally when an event occurs that is related to a specific security element our capability generally reports it."

Name: Ryan Dewhurst

Title: Founder/Developer

Page Last Updated or Reviewed: April 28, 2016