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
This month brings a WordPress 5.7.2 security release with one security issue affecting WordPress versions between 3.7 and 5.7. If you haven’t yet updated to 5.7, all WordPress versions since 3.7 have also been updated to fix an Object Injection in PHPMailer security issue.
1. WordPress 5.7.2 Security Release
Vulnerability: Object Injection in PHPMailer
Patched in Version: 5.7.2
Severity Score: Medium
WordPress Plugin Vulnerabilities
1. Funnel Builder by CartFlows
Plugin: Funnel Builder by CartFlows
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 1.6.13
Severity: Medium
2. Smooth Scroll Page Up/Down Buttons
Plugin: Smooth Scroll Page Up/Down Buttons
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 1.4
Severity Score: Medium
3. Instant Images WordPress Plugin
Plugin: Instant Images WordPress Plugin
Vulnerability: Authenticated Stored Cross-Site Scripting & XFS
Patched in Version: 4.4.0.1
Severity Score: Medium
4. CM Registration Pro
Plugin: CM Registration Pro
Vulnerability: PHP Object Injection
Patched in Version: 3.2.1
Severity Score: Medium
5. WP Prayer
Plugin: WP Prayer
Vulnerability: Authenticated Stored Cross-Site Scripting
Patched in Version: 1.6.2
Severity Score: High
6. WP Statistics
Plugin: WP Statistics
Vulnerability: Unauthenticated SQL Injection
Patched in Version: 13.0.8
Severity Score: High
7. FlightLog
Plugin: FlightLog
Vulnerability: Authenticated SQL Injection
Patched in Version: No known fix
Severity Score: High
8. Video Embed
Plugin: FlightLog
Vulnerability: Authenticated SQL Injection
Patched in Version: No known fix
Severity Score: High
WordPress Theme Vulnerabilities
1. Car Repair Services
Theme: Car Repair Services
Vulnerability: Unauthenticated Reflected Cross-Site-Scripting & XFS
Patched in Version: 4.0
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.
How to Protect Your WordPress Website From Vulnerable Plugins and Themes
The iThemes Security Pro plugin’s Site Scanner is a great way to secure and protect your WordPress website from the #1 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.
3 Types of WordPress Vulnerabilities Checked by iThemes Security Pro
- WordPress Vulnerabilities
- Plugin Vulnerabilities
- Theme Vulnerabilities
To enable the Site Scan on new installs, navigate to the iThemes Security Pro settings and click the Enable button on the Site Scan settings module.
To trigger a manual Site Scan, click the Scan Now button on the Site Scan Widget located on the right side-bar of the security settings.
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.
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.
There can be a delay between when a patch is available and the iThemes Security Vulnerability Database getting updated to reflect the fix. In this case, you can mute the notification to not receive any more alerts related to the vulnerability.
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
Catch Up on Past WordPress Vulnerability Reports for May 2021
Miss a report? Here are the reports for May 2021.
