Vulnerable plugins and themes are the #1 reason WordPress websites get hacked. The weekly WordPress Vulnerability Report powered by WPScan covers recent WordPress plugin, theme, and core vulnerabilities, and what to do if you run one of the vulnerable plugins or themes on your website.
Each vulnerability will have a severity rating of Low, Medium, High, or Critical. Responsible disclosure and reporting of vulnerabilities is an integral part of keeping the WordPress community safe. Please share this post with your friends to help get the word out and make WordPress safer for everyone.
WordPress Core Vulnerabilities
As of today, the current version of WordPress is 5.7.2. Be sure to make sure all your websites are up to date!
WordPress Plugin Vulnerabilities
1. Recently
Plugin: Recently
Vulnerability: Authenticated Code Injection
Patched in Version: 3.0.5
Severity: High
Plugin: Recently
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 3.0.5
Severity: Medium
2. WordPress Popular Posts
Plugin: WordPress Popular Posts
Vulnerability: Authenticated Code Injection
Patched in Version: 5.3.3
Severity Score: High
Plugin: WordPress Popular Posts
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 5.3.3
Severity Score: Medium
3. WP Hardening
Plugin: WP Hardening
Vulnerability: Reflected Cross-Site Scripting via URI
Patched in Version: 1.2.2
Severity Score: Medium
Plugin: WP Hardening
Vulnerability: Reflected Cross-Site Scripting via historyvalue
Patched in Version: 1.2.2
Severity Score: High
4. Comments Like Dislike
Plugin: Comments Like Dislike
Vulnerability: Add Like/Dislike Bypass
Patched in Version: 1.1.4
Severity Score: Medium
5. WP Config File Editor
Plugin: WP Config File Editor
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: No known fix
Severity Score: Medium
6. Admin Columns Free & Pro
Plugin: Admin Columns Free
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 4.3
Severity Score: Medium
Plugin: Admin Columns Pro
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 5.5.1
Severity Score: Medium
7. WP Google Maps
Plugin: WP Google Maps
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 8.1.12
Severity Score: Medium
8. Stripe Payment Gateway for WooCommerce
Plugin: Stripe Payment Gateway for WooCommerce
Vulnerability: Reflected Cross-Site Scripting
Patched in Version: 3.6.0
Severity Score: High
9. Qtranslate Slug
Plugin: Qtranslate Slug
Vulnerability: CSRF Bypass
Patched in Version: No known fix
Severity Score: Medium
10. Custom css-js-php
Plugin: Custom css-js-php
Vulnerability: CSRF Bypass
Patched in Version: No known fix
Severity Score: Medium
11. Multiple Roles
Plugin: Multiple Roles
Vulnerability: CSRF Bypass
Patched in Version: No known fix
Severity Score: Medium
12. Multivendor Marketplace Solution for WooCommerce
Plugin: Multivendor Marketplace Solution for WooCommerce
Vulnerability: CSRF Bypass
Patched in Version: 3.74
Severity Score: Medium
13. JoomSport
Plugin: JoomSport
Vulnerability: Unauthenticated PHP Object Injection
Patched in Version: 5.1.8
Severity Score: Medium
14. Smart Slider 3
Plugin: Smart Slider 3
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 3.5.0.9
Severity Score: Medium
15. Easy Cookie Policy
Plugin: Easy Cookie Policy
Vulnerability: Broken Access Control to Stored Cross-Site Scripting
Patched in Version: No known fix
Severity Score: High
16. Welcart e-Commerce
Plugin: Welcart e-Commerce
Vulnerability: Cross-Site Scripting
Patched in Version: 2.2.4
Severity Score: Medium
17. WP Prayer
Plugin: WP Prayer
Vulnerability: Arbitrary Plugin Settings Update via CSRF
Patched in Version: 1.6.7
Severity Score: Medium
WordPress Theme Vulnerabilities
1. Jannah
Theme: Jannah
Vulnerability: Reflected Cross-Site Scripting
Patched in Version: 5.4.4
Severity Score: High
2. Motor theme
Theme: Motor theme
Vulnerability: Unauthenticated Local File Inclusion
Patched in Version: 3.1.0
Severity Score: High
3. Real Estate 7
Theme: Real Estate 7
Vulnerability: 3.1.1
Patched in Version: Reflected Cross-Site Scripting
Severity Score: High
A Note on Responsible Disclosure
You might be wondering why a vulnerability would be disclosed if it gives hackers an exploit to attack. Well, it is very common for a security researcher to find and privately report the vulnerability to the software developer.
With responsible disclosure, the researcher’s initial report is made privately to the developers of the company that owns the software, but with an agreement that the full details will be published once a patch has been made available. For significant security vulnerabilities, there may be a slight delay in disclosing the vulnerability to give more people time to patch.
The security researcher may provide a deadline for the software developer to respond to the report or to provide a patch. If this deadline is not met, then the researcher may publicly disclose the vulnerability to put pressure on the developer to issue a patch.
Publicly disclosing a vulnerability and seemingly introducing a Zero-Day vulnerability–a type of vulnerability that has no patch and is being exploited in the wild– may seem counterproductive. But, it is the only leverage that a researcher has to pressure the developer to patch the vulnerability.
If a hacker were to discover the vulnerability, they could quietly use the Exploit and cause damage to the end-user(this is you), while the software developer remains content on leaving the vulnerability unpatched. Google’s Project Zero has similar guidelines when it comes to disclosing vulnerabilities. They publish the full details of the vulnerability after 90 days whether or not the vulnerability has been patched.
Get an Email Alert When iThemes Security Pro Finds a Known Vulnerability On Your Site
The iThemes Security Pro plugin’s Site Scanner is another way to secure and protect your WordPress website from the number one cause of all software hacks: outdated plugins and themes with known vulnerabilities. The Site Scanner checks your site for known vulnerabilities and automatically applies a patch if one is available.
The iThemes Security Pro plugin can email you the results of a Site Scan if it finds vulnerable plugins, themes, or WordPress core version on your site. The Site Scan results will display in the widget.
If the Site Scan detects a vulnerability, click the vulnerability link to view the details page.
Once you’ve enabled Site Scan Scheduling, head to the Notification Center settings of the plugin. On this screen, scroll to the Site Scan Results section.
Click the box to enable the notification email and then click the Save Settings button.
Now, during any scheduled site scans, you’ll get an email if iThemes Security Pro discovers any known vulnerabilities. The email will look something like this.
Get iThemes Security Pro to Secure Your Site
iThemes Security Pro, our WordPress security plugin, offers 50+ ways to secure and protect your website from common WordPress security vulnerabilities. With WordPress, two-factor authentication, brute force protection, strong password enforcement, and more, you can add an extra layer of security to your website.
Get iThemes Security Pro
Did You Miss Any of the June WordPress Vulnerability Reports?
Catch up below:
