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.
As one of the largest WordPress Vulnerability Reports to date, please share this post with your friends to help get the word out and make WordPress safer for everyone.
WordPress Core Vulnerabilities
WordPress Plugin Vulnerabilities
1. Simple Banner
Plugin: Simple Banner
Vulnerability: Authenticated Stored XSS
Patched in Version: 2.10.4
Severity Score: Low
2. HD Quiz
Plugin: HD Quiz
Vulnerability: Authenticated Stored XSS
Patched in Version: 1.8.4
Severity Score: Low
3. Contact Form 7 Captcha
Plugin: Contact Form 7 Captcha
Vulnerability: CSRF to Stored XSS
Patched in Version: 0.0.9
Severity Score: High
4. WPFront Scroll Top
Plugin: WPFront Scroll Top
Vulnerability: Authenticated Stored XSS
Patched in Version: 2.0.6.07225
Severity Score: Medium
5. WP SMS
Plugin: WP SMS
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 5.4.13
Severity Score: Low
6. Qyrr
Plugin: Qyrr
Vulnerability: Authenticated (contributor+) Stored XSS
Patched in Version: 0.7
Severity Score: Medium
7. Paid Member Subscriptions
Plugin: Paid Member Subscriptions
Vulnerability: Reflected Cross-Site Scripting (XSS)
Patched in Version: 2.4.2
Severity Score: High
Plugin: Paid Member Subscriptions
Vulnerability: Authenticated SQL Injection
Patched in Version: 2.4.2
Severity Score: Medium
8. GiveWP
Plugin: GiveWP
Vulnerability: Authenticated Stored XSS
Patched in Version: 2.12.0
Severity Score: Medium
9. Slider Hero
Plugin: Slider Hero
Vulnerability: CSRF to Stored XSS
Patched in Version: 8.2.7
Severity Score: Critical
10. Simple Social Media Share Buttons
Plugin: Simple Social Media Share Buttons
Vulnerability: Contributor+ Stored XSS
Patched in Version: 3.2.3
Severity Score: Medium
11. Advanced Shipment Tracking for WooCommerce
Plugin: Advanced Shipment Tracking for WooCommerce
Vulnerability: Authenticated Options Change
Patched in Version: 3.2.7
Severity Score: Critical
12. WP LMS
Plugin: WP LMS
Vulnerability: Unauthenticated Stored Cross-Site Scripting (XSS)
Patched in Version: 1.1.3
Severity Score: High
13. Blue Admin
Plugin: Blue Admin
Vulnerability: CSRF to Stored Cross-Site Scripting (XSS)
Patched in Version: No known fix
Severity Score: High
14. Favicon by RealFaviconGenerator
Plugin: Favicon by RealFaviconGenerator
Vulnerability: Reflected Cross-Site Scripting (XSS)
Patched in Version: No known fix
Severity Score: High
15. uListing
Plugin: uListing
Vulnerability: Unauthenticated SQL Injection
Patched in Version: 2.0.4
Severity Score: High
Plugin: uListing
Vulnerability: Authenticated IDOR
Patched in Version: 2.0.6
Severity Score: Medium
Plugin: uListing
Vulnerability: Authenticated Reflected XSS
Patched in Version: 2.0.6
Severity Score: Low
Plugin: uListing
Vulnerability: Multiple CSRF
Patched in Version: 2.0.6
Severity Score: Medium
Plugin: uListing
Vulnerability: Modify User Roles via CSRF
Patched in Version: 2.0.6
Severity Score: Medium
Plugin: uListing
Vulnerability: Settings Update via CSRF
Patched in Version: 2.0.6
Severity Score: Medium
Plugin: uListing
Vulnerability: Unauthenticated Privilege Escalation
Patched in Version: 2.0.6
Severity Score: Medium
16. WooCommerce Blocks 2.5 to 5.5
Plugin: WooCommerce Blocks 2.5 to 5.5
Vulnerability: Unauthenticated SQL Injection
Patched in Version: 5.5.1
Severity Score: Critical
17. Woocommerce 3.3 to 5.5
Plugin: Woocommerce 3.3 to 5.5
Vulnerability: Authenticated Blind SQL Injection
Patched in Version: 5.5.1
Severity Score: High
18. Admin Custom Login
Plugin: Admin Custom Login
Vulnerability: CSRF to Stored XSS
Patched in Version: 3.2.8
Severity Score: High
19. SEO Backlinks
Plugin: SEO Backlinks
Vulnerability: CSRF to Stored XSS
Patched in Version: No known fix
Severity Score: High
20. Poll Maker
Plugin: Poll Maker
Vulnerability: Reflected Cross-Site Scripting
Patched in Version: 3.2.9
Severity Score: High
21. Post Index
Plugin: Post Index
Vulnerability: CSRF to Stored XSS
Patched in Version: No known fix
Severity Score: High
22. Side Menu Lite
Plugin: Side Menu Lite
Vulnerability: Authenticated SQL Injection
Patched in Version: 2.2.6
Severity Score: High
23. WordPress Download Manager
Plugin: WordPress Download Manager
Vulnerability: Authenticated Directory Traversal
Patched in Version: 3.1.25
Severity Score: Medium
Plugin: WordPress Download Manager
Vulnerability: Authenticated File Upload
Patched in Version: 3.1.25
Severity Score: Medium
24. FluentSMTP
Plugin: FluentSMTP
Vulnerability: Authenticated Stored XSS
Patched in Version: 2.0.1
Severity Score: Low
25. Youtube Feeder
Plugin: Youtube Feeder
Vulnerability: CSRF to Stored XSS
Patched in Version: No known fix
Severity Score: High
26. Nifty Newsletters
Plugin: Nifty Newsletters
Vulnerability: CSRF to Stored XSS
Patched in Version: No known fix
Severity Score: High
WordPress Theme Vulnerabilities
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.
How to Protect Your WordPress Website From Vulnerable Plugins and Themes
As you can see from this report, lots of new WordPress plugin and theme vulnerabilities are disclosed each week. We know it can be difficult to stay on top of every reported vulnerability disclosure, so the iThemes Security Pro plugin makes it easy to make sure your site isn’t running a theme, plugin or WordPress core version with a known vulnerability.
1. Turn on the iThemes Security Pro Site Scanner
The iThemes Security Pro plugin’s Site Scanner scans for the #1 reason WordPress sites get hacked: 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.
To enable the Site Scan on new installs, navigate to the Site Check tab on the Features menu inside the plugin and click the toggle to enable the Site Scan.
To trigger a manual Site Scan, click the Scan Now button on the Site Scan Security Dashboard card.
If the Site Scan detects a vulnerability, click the vulnerability link to view the details page.
On the Site Scan vulnerability page, you will see if there is a fix available for the vulnerability. If there is a patch available, you can click the Update Plugin button to apply the fix on your website.
2. Turn on Version Management
The Version Management feature in iThemes Security Pro integrates with the Site Scan to protect your site when outdated software is not updated quickly enough. Even the strongest security measures will fail if you are running vulnerable software on your website. These settings help protect your site with options to update to new versions automatically if a known vulnerability exists and a patch is available.
From the Settings page in iThemes Security Pro, navigate to the Features screen. Click the Site Check tab. From here, use the toggle to enable Version Management. Using the settings gear, you can configure even more settings, including how you want iThemes Security Pro to handle updates to WordPress, plugins, themes, and additional protection.
Make sure to select Auto Update if it Fixes a Vulnerability box so that iThemes Security Pro will automatically update a plugin or theme if it fixes a vulnerability that was found by the Site Scanner.
3. Get an Email Alert When iThemes Security Pro Finds a Known Vulnerability On Your Site
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 and Rest a Little Easier Tonight
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.
.wp-block-kadence-iconlist.kt-svg-icon-list-items_f826f1-b6:not(.this-stops-third-party-issues) {margin-top:0}.wp-block-kadence-iconlist.kt-svg-icon-list-items_f826f1-b6 ul.kt-svg-icon-list {margin:0px 0px 10px 50px;}
Get iThemes Security Pro
The post WordPress Vulnerability Report: August 2021, Part 1 appeared first on iThemes.
Source: Security Feed