Home Plans Products
Tools
Technology Trends Keyword Lists Browser Extensions
Features
Lead Generation Market Analysis Sales Intelligence
Resources
FAQ About Contact Blog
Account
Login Sign up
Home / Blog / wordpress 4.2.2
Security Advisory

WordPress 4.2.2 Security: 28 CVEs Explained & How to Fix

📅 June 07, 2026 ·⏱ 5 min read ·🔒 SiteRecipe Security Team
77 websites still running wordpress 4.2.2  → View full list
28
Total
1
Critical
3
High
22
Medium
2
Low

WordPress 4.2.2 is an older version of the world's most popular website platform, released years ago. If your website still runs this version, you're at significant risk. Security researchers have discovered 28 vulnerabilities in this release, including 1 critical flaw that could allow hackers to take complete control of your site. This guide will help you understand these threats and protect your website immediately.

Despite being outdated, approximately 77 websites worldwide still use WordPress 4.2.2. These sites face daily threats from automated attacks targeting known vulnerabilities. The good news is that identifying and fixing these issues is straightforward if you follow the right steps. We'll walk you through everything you need to know.

What is Wordpress 4.2.2?

WordPress 4.2.2 is an older version of WordPress, the software that powers over 40% of all websites on the internet. WordPress allows non-technical users to create, manage, and publish content on their websites without coding knowledge. Version 4.2.2 was released in 2015 and hasn't received security updates in years. Think of WordPress as the foundation of your home—if you don't maintain it, cracks will develop and let intruders in.

When WordPress releases new versions, they fix security problems discovered in older versions. Using outdated software is like leaving your front door unlocked. Hackers use automated tools to scan the internet for websites running vulnerable versions like 4.2.2, then exploit known weaknesses to steal data, inject malware, or deface content. Updating to the latest WordPress version closes these doors and protects your visitors' information.

Key Vulnerabilities in Wordpress 4.2.2

28 CVEs found. The most critical are explained below.

CRITICAL CVE-2020-36847 9.8/10 · CVSS v3.1 ⏱ Immediate
Simple File List Plugin - Hackers Can Run Code on Your Site

The Simple File List plugin has a serious flaw that lets anyone upload a file and trick the system into running it as code. This happens because the plugin doesn't properly check file types when renaming uploaded files. Attackers don't need a login to exploit this.

Impact: A hacker could take complete control of your website, steal data, inject malware, or use your site to attack other websites.

↗ View on NVD
HIGH CVE-2026-2052 8.8/10 · CVSS v3.1 ⏱ Immediate
Widget Options Plugin - Code Execution Through Display Settings

The Widget Options plugin processes display settings in an unsafe way that allows attackers to inject and run malicious code. This affects how widgets appear on your pages and can be exploited without requiring special permissions.

Impact: Attackers could execute harmful code on your server, potentially compromising your entire website and visitor data.

↗ View on NVD
HIGH CVE-2020-11026 8.7/10 · CVSS v3.1 ⏱ Within 7 days
WordPress Media Upload - Code Execution via File Names

WordPress can execute code when you upload files with specially crafted names to the Media section. Only users who can upload files (like editors or admins) can trigger this, but it poses a risk if these accounts are compromised.

Impact: Someone with upload access could run malicious code on your server and compromise your website.

↗ View on NVD
HIGH CVE-2026-5217 7.2/10 · CVSS v3.1 ⏱ Within 7 days
Optimole Plugin - Code Injection in Search Settings

The Optimole image optimization plugin doesn't properly filter input in its search feature, allowing attackers to inject malicious code that runs when others view the affected pages. This code stays permanently stored on your site.

Impact: Attackers could inject malware or steal information from your visitors' browsers.

↗ View on NVD
MEDIUM CVE-2020-4047 6.8/10 · CVSS v3.1 ⏱ Within 30 days
WordPress Media Pages - JavaScript Injection by Authors

Authors and other users with upload permissions can inject malicious JavaScript code into media attachment pages. When an admin views these pages, the code runs with admin privileges, potentially granting attackers higher access.

Impact: A compromised author account could be used to gain admin-level access to your website.

↗ View on NVD
MEDIUM CVE-2022-1827 6.5/10 · CVSS v3.1 ⏱ Within 30 days
PDF24 Plugin - Settings Can Be Changed Without Permission

The PDF24 plugin lacks a security check that prevents attackers from tricking logged-in admins into changing plugin settings without their knowledge. An attacker could send a malicious link that changes settings when clicked.

Impact: Attackers could alter how your PDF conversion plugin works, potentially injecting malware or disrupting your site functionality.

↗ View on NVD

Additional Vulnerabilities (22 more)

Showing first 10 of 22. View all on NVD ↗

CVE IDSeverityScore PublishedDescription
CVE-2022-1828 MEDIUM 6.5 2022-06-20 The PDF24 Articles To PDF WordPress plugin through 4.2.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change…
CVE-2020-11030 MEDIUM 6.4 2020-04-30 In affected versions of WordPress, a special payload can be crafted that can lead to scripts getting executed within the search block of the block editor. This requires an authent…
CVE-2025-14865 MEDIUM 6.4 2026-01-28 The Passster – Password Protect Pages and Content plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'content_protector' shortcode in all versions …
CVE-2015-8834 MEDIUM 6.1 2016-05-22 Cross-site scripting (XSS) vulnerability in wp-includes/wp-db.php in WordPress before 4.2.2 allows remote attackers to inject arbitrary web script or HTML via a long comment that …
CVE-2020-11027 MEDIUM 6.1 2020-04-30 In affected versions of WordPress, a password reset link emailed to a user does not expire upon changing the user password. Access would be needed to the email account of the user…
CVE-2020-11025 MEDIUM 5.8 2020-04-30 In affected versions of WordPress, a cross-site scripting (XSS) vulnerability in the navigation section of Customizer allows JavaScript code to be executed. Exploitation requires …
CVE-2020-11028 MEDIUM 5.8 2020-04-30 In affected versions of WordPress, some private posts, which were previously public, can result in unauthenticated disclosure under a specific set of conditions. This has been pat…
CVE-2020-11029 MEDIUM 5.8 2020-04-30 In affected versions of WordPress, a vulnerability in the stats() method of class-wp-object-cache.php can be exploited to execute cross-site scripting (XSS) attacks. This has been…
CVE-2020-4048 MEDIUM 5.7 2020-06-12 In affected versions of WordPress, due to an issue in wp_validate_redirect() and URL sanitization, an arbitrary external link can be crafted leading to unintended/open redirect wh…
CVE-2020-4046 MEDIUM 5.4 2020-06-12 In affected versions of WordPress, users with low privileges (like contributors and authors) can use the embed block in a certain way to inject unfiltered HTML in the block editor…
Full Report Available

All 28 CVEs with AI explanations + fix guide

Plain English · Fix recommendations · Instant PDF & HTML download

⬇ Get Full Report
PDF + HTML · Instant download

Is your website running Wordpress 4.2.2?

Scan your site in 30 seconds. Used by 500+ web agencies.

How to Check If Your Website Is Affected

How to Fix These Vulnerabilities

Conclusion

WordPress 4.2.2 contains serious security vulnerabilities that put your website, customer data, and reputation at risk. The 1 critical vulnerability alone could give hackers complete access to your site. Updating to the latest WordPress version takes just minutes and is one of the most important maintenance tasks you can do. Don't wait for a breach—take action today.

SiteRecipe.com offers free security scanning that instantly tells you which WordPress version you're running and alerts you to any known vulnerabilities on your site. Our experts can also guide you through the update process step-by-step. Visit SiteRecipe.com now to scan your website for free and get personalized recommendations to keep your site secure, fast, and fully protected against threats.

Frequently Asked Questions

Will updating WordPress 4.2.2 break my website?
Not if you follow the proper steps. Always back up your website first, update plugins and themes, then update WordPress. Most websites update seamlessly, and our team at SiteRecipe.com can guide you through any issues that arise.
What happens if I don't update from WordPress 4.2.2?
Your site remains vulnerable to known attacks. Hackers actively exploit these old vulnerabilities to steal data, insert malware, or take over websites completely. Updating is the most critical security step you can take.
Can I update WordPress 4.2.2 automatically?
WordPress offers automatic updates for newer versions, but manual updates give you more control and the ability to test your site first. Either way, always back up before updating to ensure you can restore your site if needed.
How often should I update WordPress after upgrading from 4.2.2?
Enable automatic updates for minor security releases, and manually update to major versions as they're released (typically every few months). Regular updates patch vulnerabilities immediately after they're discovered.
What if I can't update due to custom code or old plugins?
Contact your web developer to update incompatible code, or consider migrating to a new hosting platform with better plugin support. Staying on 4.2.2 is far riskier than fixing compatibility issues.

Generate white-label reports for your clients

Web agencies use SiteRecipe to produce branded PDF security reports in 30 seconds.

DISCLAIMER: This report is based on publicly available CVE data from the National Vulnerability Database (NVD) maintained by NIST. Detection of a technology version does not confirm active exploitation on any specific website. For informational purposes only. SiteRecipe is not responsible for actions taken based on this report. Always consult a qualified security professional.

Source: nvd.nist.gov · Published: June 07, 2026 · SiteRecipe.com