Author Archives: wpscanteam

We’ve been alerted that certain vendors are using suboptimal secret management techniques to handle (H/T)OTP encryption keys, which leads to them not bringing any additional security value. Examples we’ve received include storing the encryption key on the database alongside the shared secret it encrypted or using the same key for all sites using the plugin.…More

We receive a non-negligible amount of submissions every day. We model the risk they represent for site owners, figure out what kind of privilege is required to successfully exploit the issue, and forward the information to plugin and theme authors to get it fixed. This is can get pretty time-consuming, especially when we need to…More

We are very excited to let you know that WPScan will be joining Automattic! WPScan has been working on improving the WordPress security ecosystem for over 10 years. During that time we released our wildly popular WordPress security scanner. We then developed and released the WordPress vulnerability database, where we triage and record hundreds of…More

Bit Discovery have been using the WPScan WordPress security scanner and the WPScan Enterprise API for some time to add WordPress scanning functionality to their offering. We thought that it would be a good idea to introduce our readers to what Attack Surface Mapping is, and how organisations can benefit from it. To do this,…More

WPScan has collaborated with Wordfence to conduct a 2021 mid-year review on the state of WordPress security. Using vulnerability data from WPScan’s WordPress vulnerability database and attack data from Wordfence’s internal threat intelligence platform, we were able to analyze the current trend of attacks on WordPress and assess the current state of WordPress-based software security. …More

There are many reasons to submit WordPress core, plugin vulnerabilities and theme vulnerabilities to the WPScan WordPress vulnerability database. We’ve listed just a few below! 1. Responsible Disclosure Our team will help you with the vulnerability responsible disclosure process. Submit the vulnerability details to us and we will ensure that the vulnerability is handled properly.…More

In this blog post we are going to look at the vulnerabilities added to the WPScan WordPress Vulnerability Database in July 2021. The vulnerabilities were all hand curated and added to our database by WordPress security experts. The vulnerabilities come from independent security researchers from the security community who submit them to us via our…More

By default, WordPress allows administrator and editor users to inject JavaScript into pages, posts, comments and widgets. This is because administrator and editor users have the unfiltered_html capability. Here at WPScan it is quite common to receive vulnerability reports via our submission form where the security researcher was not aware that administrator and editor users…More

In March, the WPScan WordPress security research team discovered Cross-Site Request Forgery (CSRF) protection bypasses in 37 WordPress plugins, affecting over 200,000+ active WordPress websites. The vulnerabilities were responsibly disclosed, resulting in the 37 plugins either being patched or removed from the official WordPress plugin repository. Cross-Site Request Forgery (CSRF) is a vulnerability that can…More