=== WPVulnerability ===
Contributors: javiercasares, davidperez, lbonomo, alexclassroom
Tags: security, vulnerability, site-health
Requires at least: 4.1
Tested up to: 6.7
Stable tag: 3.4.1
Requires PHP: 5.6
Version: 3.4.1
License: GPL-2.0-or-later
License URI: https://spdx.org/licenses/GPL-2.0-or-later.html

Get WordPress vulnerability alerts from [WordPress Vulnerability Database API](https://www.wpvulnerability.com/).

== Description ==

This plugin integrates with the WPVulnerability API to provide real-time vulnerability assessments for your WordPress core, plugins, themes, PHP version, Apache HTTPD, nginx, MariaDB, and MySQL. It delivers detailed reports directly within your WordPress dashboard, helping you stay aware of potential security risks. Configure the plugin to send periodic notifications about your site's security status, ensuring you remain informed without being overwhelmed. Designed for ease of use, it supports proactive security measures without storing or retrieving any personal data from your site.

= Data reliability =

The information provided by the information database comes from different sources that have been reviewed by third parties. There is no liability of any kind for the information. Act at your own risk.

== Using the plugin ==

= WP-CLI =

You can use the following WP-CLI commands to manage and check vulnerabilities:

* `wp wpvulnerability core`: Displays Core vulnerabilities.
* `wp wpvulnerability plugins`: Displays Plugins vulnerabilities.
* `wp wpvulnerability themes`: Displays Themes vulnerabilities.
* `wp wpvulnerability php`: Displays PHP vulnerabilities.
* `wp wpvulnerability apache`: Displays Apache HTTPD vulnerabilities.
* `wp wpvulnerability nginx`: Displays nginx vulnerabilities.
* `wp wpvulnerability mariadb`: Displays MariaDB vulnerabilities.
* `wp wpvulnerability mysql`: Displays MySQL vulnerabilities.

All commands support the `--format` option to specify the output format:

* `--format=table`: Displays the results in a table format (default).
* `--format=json`: Displays the results in JSON format.

Need help?

* `wp wpvulnerability --help`: Displays help information for WPVulnerability commands.
* `wp wpvulnerability [command] --help`: Displays help information for a WPVulnerability command.

= REST API =

The WPVulnerability plugin provides several REST API endpoints to fetch vulnerability information for different components of your WordPress site.

* `/wpvulnerability/v1/core`: Fetches Core vulnerabilities.
* `/wpvulnerability/v1/plugins`: Fetches Plugins vulnerabilities.
* `/wpvulnerability/v1/themes`: Fetches Themes vulnerabilities.
* `/wpvulnerability/v1/php`: Fetches PHP vulnerabilities.
* `/wpvulnerability/v1/apache`: Fetches Apache HTTPD vulnerabilities.
* `/wpvulnerability/v1/nginx`: Fetches nginx vulnerabilities.
* `/wpvulnerability/v1/mariadb`: Fetches nginx vulnerabilities.
* `/wpvulnerability/v1/mysql`: Fetches nginx vulnerabilities.

Authentication

The WPVulnerability REST API uses Application Passwords for authentication. You need to include a valid Application Password in the Authorization header of your requests.

Example Request with Authentication

`curl -X GET https://example.com/wp-json/wpvulnerability/v1/plugins -u username:application_password`

Replace username with your WordPress `username` and `application_password` with your [Application Password](https://make.wordpress.org/core/2020/11/05/application-passwords-integration-guide/).

== Extra Configurations ==

= "From:" mail (since: 3.2.2) =

If, for some reason, you need the emails sent by the plugin to have a From different from the site administrator, you can change it from the `wp-config.php` by adding a constant:

`define( 'WPVULNERABILITY_MAIL', 'sender@example.com' );`

If the constant is active, it will be visible in the configuration screen.

== Installation ==

= Automatic download =

Visit the plugin section in your WordPress, search for [wpvulnerability]; download and install the plugin.

= Manual download =

Extract the contents of the ZIP and upload the contents to the `/wp-content/plugins/wpvulnerability/` directory. Once uploaded, it will appear in your plugin list.

== Frequently Asked Questions ==

= Where does the vulnerability information come from? =

The origin is in the WPVulnerability.com API. The vulnerabilities that appear in this API come from different sources, such as CVEs.

= Is data from my site sent anywhere? =

No. Never. Your privacy is very important to us. We do not commercialize with your data.

= What vulnerabilities will I find? =

Vulnerabilities in WordPress Core, Plugins, Themes, PHP, Apache HTTPD, and nginx are documented.

= What do I do if my site has a vulnerability? =

First of all, peace of mind. Investigate what the vulnerability is and, above all, check that you have the latest version of the compromised element. We actively recommend that you keep all your WordPress and its plugins up to date.

== Screenshots ==

1. WP-Admin Dashboard widget.
2. Vulnerability list at Site Health.
3. Vulnerability list at Plugins list.

== Compatibility ==

* WordPress: 4.1 - 6.7
* PHP: 5.6 - 8.3
* WP-CLI: 2.3.0 - 2.11.0

== Changelog ==

= [3.4.1] - 2024-08-23 =

**Fixed**

* The number of vulnerabilities for core is incorrect.

**Compatibility**

* WordPress: 4.1 - 6.7
* PHP: 5.6 - 8.3
* WP-CLI: 2.3.0 - 2.11.0

**Tests**

* PHP Coding Standards: 3.10.2
* WordPress Coding Standards: 3.1.0
* Plugin Check (PCP): 1.0.2
* SonarCloud Code Review

= [3.4.0] - 2024-08-16 =

**Added**

* New checks for MariaDB vulnerabilities.
* New checks for MySQL vulnerabilities.
* WPVulnerability statistics in the configuration page.
* WPVulnerability contributors in the configuration page.

**Changed**

* Code improvement.
* Better UI for the configuration page.
* Web server version detection improved.

**Fixed**

* Get the statistics information the right way.

**Compatibility**

* WordPress: 4.1 - 6.7
* PHP: 5.6 - 8.3
* WP-CLI: 2.3.0 - 2.11.0

**Tests**

* PHP Coding Standards: 3.10.2
* WordPress Coding Standards: 3.1.0
* Plugin Check (PCP): 1.0.2
* SonarCloud Code Review

= [3.3.5] - 2024-08-14 =

**Added**

* Add counters for Core, Plugins, and Themes.
* Add a Vulnerabilities filter in the Plugin list (WordPress and WordPress Multisite).
* Add a Vulnerabilities filter in the Themes list (WordPress Multisite).

**Compatibility**

* WordPress: 4.1 - 6.7
* PHP: 5.6 - 8.3
* WP-CLI: 2.3.0 - 2.11.0

**Tests**

* PHP Coding Standards: 3.10.2
* WordPress Coding Standards: 3.1.0
* Plugin Check (PCP): 1.0.2
* SonarCloud Code Review

= Previous versions =

If you want to see the full changelog, visit the [changelog.txt](https://plugins.trac.wordpress.org/browser/wpvulnerability/trunk/changelog.txt) file.

== Security ==

This plugin adheres to the following security measures and review protocols for each version:

* [WordPress Plugin Handbook](https://developer.wordpress.org/plugins/)
* [WordPress Plugin Security](https://developer.wordpress.org/plugins/wordpress-org/plugin-security/)
* [WordPress APIs Security](https://developer.wordpress.org/apis/security/)
* [WordPress Coding Standards](https://github.com/WordPress/WordPress-Coding-Standards)
* [Plugin Check (PCP)](https://wordpress.org/plugins/plugin-check/)
* [SonarCloud Code Review](https://www.sonarsource.com/products/sonarcloud/)

== Privacy ==

* This plugin or the WordPress Vulnerability Database API does not collect any information about your site, your identity, the plugins, themes or content the site has.

== Vulnerabilities ==

* No vulnerabilities have been published up to version 3.4.1.

Found a security vulnerability? Please report it to us privately at the [WPVulnerability GitHub repository](https://github.com/javiercasares/wpvulnerability/security/advisories/new).

== Contributors ==

You can contribute to this plugin at the [WPVulnerability GitHub repository](https://github.com/javiercasares/wpvulnerability).