WordPress Vulnerability Report: July 2021, Part 3

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.

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.

In the July, Part 3 Report
Sign up for the weekly WordPress Security News & Updates newsletter

WordPress Core Vulnerabilities

WordPress Plugin Vulnerabilities

1. Woocommerce

Plugin: WooCommerce 3.3 to 5.5
Vulnerability: Authenticated SQL Injection
Patched in Version: 5.5.1

The vulnerability is patched, so you should update to version 5.5.1.

2. Woocommerce Blocks

Plugin: WooCommerce Blocks 2.5 to 5.5
Vulnerability: Unauthenticated SQL Injection
Patched in Version: 5.5.1

The vulnerability is patched, so you should update to version 5.5.1.

3. Advanced Menu Manager

Plugin: Advanced Menu Manager
Vulnerability: Unauthorised Menu Creation/Deletion
Patched in Version: No known fix – Plugin Closed 

Plugin: Advanced Menu Manager
Vulnerability: Unauthorised Menu CEdition via CSRF
Patched in Version: No known fix – Plugin Closed

Uninstall and delete the plugin until a patch is released.

4. Wr Age Verification

vulnerability report WR Age Verification

Plugin: Wr Age Verification
Vulnerability: Reflected Cross-Site Scripting (XSS)
Patched in Version: 2.0.0

The vulnerability is patched, so you should update to version 2.0.0.

5. Marmoset Viewer

Plugin: Marmoset Viewer
Vulnerability: Reflected Cross-Site Scripting
Patched in Version: 1.9.3

The vulnerability is patched, so you should update to version 1.9.3.

6. WOWRestro

Plugin: WOWRestro
Vulnerability: CSRF Bypass
Patched in Version: 1.1

The vulnerability is patched, so you should update to version 1.1.

7. Page View Counts

Plugin: Page View Counts
Vulnerability: Contributor+ Stored Cross-Site Scripting (XSS)
Patched in Version: 2.4.9

The vulnerability is patched, so you should update to version 2.4.9.

8. Frontend File Manager

Plugin: Frontend File Manager
Vulnerability: Privilege Escalation
Patched in Version: 18.3

Plugin: Frontend File Manager
Vulnerability: Unauthenticated Content Injection and Stored XSS
Patched in Version: 18.3

Plugin: Frontend File Manager
Vulnerability: Authenticated Arbitrary Settings Change to Arbitrary File Upload
Patched in Version: 18.3

Plugin: Frontend File Manager
Vulnerability: Unauthenticated Arbitrary Post Deletion
Patched in Version: 18.3

Plugin: Frontend File Manager
Vulnerability: Unauthenticated Post Meta Change to Arbitrary File Download
Patched in Version: 18.3

Plugin: Frontend File Manager
Vulnerability: Unauthenticated HTML Injection
Patched in Version: 18.3

The vulnerability is patched, so you should update to version 18.3.

9. Stock in & out

Plugin: Stock in & out
Vulnerability: Authenticated SQL Injection
Patched in Version: No known fix – Plugin Closed 
Severity Score:

Plugin: Stock in & out
Vulnerability: Reflected Cross-Site Scripting (XSS)
Patched in Version: No known fix – Plugin Closed
Severity Score:

Uninstall and delete the plugin until a patch is released.

10. Side Menu Lite – add sticky fixed buttons

Plugin: Side Menu Lite
Vulnerability: Authenticated SQL Injection
Patched in Version: 2.2.1

The vulnerability is patched, so you should update to version 2.2.1.

11. ProfilePress

Plugin: ProfilePress
Vulnerability: Unauthenticated Cross-Site Scripting (XSS)
Patched in Version: 3.1.11

The vulnerability is patched, so you should update to version 3.1.11.

12. WP Google Map

Plugin: WP Google Map
Vulnerability: Authenticated Stored Cross-Site Scripting (XSS)
Patched in Version: 1.7.7

The vulnerability is patched, so you should update to version 1.7.7.

13. 10Web Map Builder for Google Maps

Plugin: 10Web Map Builder for Google Maps
Vulnerability: Authenticated Stored XSS
Patched in Version: 1.0.70

The vulnerability is patched, so you should update to version 1.0.70.

14. Video Posts Webcam Recorder

Plugin: Video Posts Webcam Recorder
Vulnerability: Authenticated Reflected XSS
Patched in Version: 3.2.4

The vulnerability is patched, so you should update to version 3.2.4.

15. WPFront Notification Bar

Plugin: WPFront Notification Bar
Vulnerability: Authenticated Stored XSS
Patched in Version: 2.0.0.07176

The vulnerability is patched, so you should update to version 2.0.0.07176.

Plugin: WordPress Popular Posts
Vulnerability: Authenticated Code Injection
Patched in Version: 5.3.3

The vulnerability is patched, so you should update to version 5.3.3.

17. Form Maker by 10Web

Plugin: Form Maker by 10Web
Vulnerability: Authenticated Stored XSS
Patched in Version: 1.13.60

The vulnerability is patched, so you should update to version 1.13.60.

18. Activity Log

Plugin: Activity Log
Vulnerability: Authenticated SQL Injection
Patched in Version: 2.7.0

The vulnerability is patched, so you should update to version 2.7.0.

19. Current Book

Plugin: Current Book
Vulnerability: Authenticated Stored Cross-Site Scripting (XSS)
Patched in Version: No known fix – Plugin Closed

Uninstall and delete the plugin until a patch is released.

20. ECPay Logistics for WooCommerce

Plugin: ECPay Logistics for WooCommerce
Vulnerability: Unauthenticated Reflected XSS
Patched in Version: 1.3.1910240

The vulnerability is patched, so you should update to version 1.3.1910240.

21. Event Espresso Core

Plugin: Event Espresso Core
Vulnerability: Reflected Cross-Site Scripting (XSS)
Patched in Version: 4.10.7.p

The vulnerability is patched, so you should update to version 4.10.7.p.

WordPress Theme Vulnerabilities

1. Newsmag

Plugin: Newsmag
Vulnerability: Unauthenticated Reflected Cross-site Scripting (XSS)
Patched in Version: 5.0
Severity Score:

The vulnerability is patched, so you should update to version 5.0.

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 to Auto Update if Fixes Vulnerability

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.

iThemes Security Pro version management

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.

site-scan-results
Important: You should not mute a vulnerability notification until you have confirmed your current version includes a security fix, or the vulnerability doesn’t affect your site.

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 extra layers of security to your website.

Get iThemes Security Pro

Each week, Michael puts together the WordPress Vulnerability Report to help keep your sites safe. As Product Manager at iThemes, he helps us continue to improve the iThemes product lineup. He’s a giant nerd & loves learning about all things tech, old & new. You can find Michael hanging out with his wife & daughter, reading or listening to music when not working.

wordpress vulnerability report

Spread the love

Posted by News Monkey

blank