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.5
Security Advisory

WordPress 4.5: 156 CVEs Found - Security Update Guide

📅 June 07, 2026 ·⏱ 5 min read ·🔒 SiteRecipe Security Team
19 websites still running wordpress 4.5  → View full list
156
Total
6
Critical
27
High
120
Medium
3
Low

WordPress 4.5, released in 2016, is now considered a significant security risk with 156 documented vulnerabilities discovered across multiple plugins and themes. If your website is still running this outdated version, you're exposing your business to serious threats including remote code execution, arbitrary file uploads, and unauthorized access. This comprehensive guide will help you identify if you're vulnerable and take immediate action to protect your site.

The severity of these vulnerabilities cannot be overstated. Six critical-level CVEs affect popular plugins like Nelio A/B Testing, Divi Builder, GEO my WP, and OMGF, allowing attackers to execute malicious code, upload dangerous files, and compromise your entire WordPress installation. Even if you're not directly using these plugins, your server and data are at risk if WordPress 4.5 remains unpatched.

What is Wordpress 4.5?

WordPress 4.5 was released in April 2016 and marked a significant milestone for the platform with the introduction of the REST API and improved mobile editing capabilities. However, the version has long since passed its support lifecycle, meaning WordPress developers no longer release security patches or updates for it. This makes WordPress 4.5 an increasingly dangerous choice for website owners who rely on the platform for their online presence.

Thinking of WordPress versions like software on your computer: just as Windows or macOS require regular updates to stay secure, WordPress versions need continuous patches to protect against newly discovered threats. WordPress 4.5 is essentially running without security updates, making it vulnerable to every new attack discovered since 2016. Whether you're running a personal blog or a business website, staying on WordPress 4.5 puts your entire digital presence at risk.

Key Vulnerabilities in Wordpress 4.5

156 CVEs found. The most critical are explained below.

CRITICAL CVE-2016-10926 10.0/10 · CVSS v3.0 ⏱ Immediate
Nelio A/B Testing Plugin - Server Attack Vulnerability

The Nelio A/B Testing plugin before version 4.5.9 has a security flaw that allows attackers to make your server request files from other websites or internal systems. This happens through a feature in the plugin's code that doesn't properly validate where requests are being sent.

Impact: An attacker could use your website's server to access sensitive information, attack other websites, or bypass security measures. This could damage your website's reputation and potentially expose private data.

↗ View on NVD
CRITICAL CVE-2016-10927 10.0/10 · CVSS v3.0 ⏱ Immediate
Nelio A/B Testing Plugin - Server Attack Vulnerability (Updated)

Similar to CVE-2016-10926, the Nelio A/B Testing plugin before version 4.5.11 contains the same server-based attack flaw. Even though version 4.5.9 was patched, a newer update to 4.5.11 is required for complete protection.

Impact: Your server could be misused to attack other systems or retrieve unauthorized information. This puts your website at risk of legal liability and loss of customer trust.

↗ View on NVD
CRITICAL CVE-2020-35945 9.9/10 · CVSS v3.1 ⏱ Immediate
Divi Builder - Malicious File Upload Vulnerability

The Divi Builder plugin before version 4.5.3 allows authorized users (like content editors) to upload dangerous files like executable PHP scripts instead of just images or documents. The safety check only exists on your browser, not on the server where it matters.

Impact: A compromised or malicious team member could upload code that takes over your entire website, steals customer data, or turns your site into a malware distribution point.

↗ View on NVD
CRITICAL CVE-2024-6330 9.8/10 · CVSS v3.1 ⏱ Immediate
GEO my WP Plugin - Unauthorized Code Execution

The GEO my WP plugin before version 4.5.0.2 fails to block unauthorized users from including and running malicious code through file manipulation. Anyone, even without a website account, can trigger this vulnerability.

Impact: Attackers can execute arbitrary code on your server, giving them complete control over your website, customer data, and server resources. This is one of the most severe types of attacks possible.

↗ View on NVD
CRITICAL CVE-2021-24638 9.1/10 · CVSS v3.1 ⏱ Immediate
OMGF Plugin - CSS File Overwrite & Download Vulnerability

The OMGF plugin before version 4.5.4 doesn't properly secure its file handling, allowing unauthenticated attackers to manipulate file paths and overwrite your CSS files or download Google Fonts. This happens because user input isn't validated.

Impact: Attackers could deface your website's appearance, redirect visitors to malicious sites, or access files they shouldn't have. This could damage user trust and lead to further security breaches.

↗ View on NVD
CRITICAL CVE-2025-54677 9.1/10 · CVSS v3.1 ⏱ Immediate
vcita Booking Plugin - Dangerous File Upload Vulnerability

The vcita Online Booking plugin through version 4.5.3 allows attackers to upload malicious files without proper restrictions. There's no adequate check to prevent uploading executable or dangerous file types.

Impact: Attackers could upload malware, ransomware, or other harmful files that compromise your website and endanger your customers' information and devices.

↗ View on NVD

Additional Vulnerabilities (150 more)

Showing first 10 of 150. View all on NVD ↗

CVE IDSeverityScore PublishedDescription
CVE-2016-6635 HIGH 8.8 2016-08-07 Cross-site request forgery (CSRF) vulnerability in the wp_ajax_wp_compression_test function in wp-admin/includes/ajax-actions.php in WordPress before 4.5 allows remote attackers t…
CVE-2021-24711 HIGH 8.8 2021-10-11 The del_reistered_domains AJAX action of the Software License Manager WordPress plugin before 4.5.1 does not have any CSRF checks, and is vulnerable to a CSRF attack
CVE-2021-39317 HIGH 8.8 2021-10-11 A WordPress plugin and several WordPress themes developed by AccessPress Themes are vulnerable to malicious file uploads via the plugin_offline_installer AJAX action due to a miss…
CVE-2021-24631 HIGH 8.8 2021-11-08 The Unlimited PopUps WordPress plugin through 4.5.3 does not sanitise or escape the did GET parameter before using it in a SQL statement, available to users as low as editor, lead…
CVE-2023-0875 HIGH 8.8 2023-03-20 The WP Meta SEO WordPress plugin before 4.5.3 does not properly sanitize and escape inputs into SQL queries, leading to a blind SQL Injection vulnerability that can be exploited b…
CVE-2023-1381 HIGH 8.8 2023-04-10 The WP Meta SEO WordPress plugin before 4.5.5 does not validate image file paths before attempting to manipulate the image files, leading to a PHAR deserialization vulnerability. …
CVE-2025-12028 HIGH 8.8 2025-10-24 The IndieAuth plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.5.4. This is due to missing nonce verification on the `login…
CVE-2025-12966 HIGH 8.8 2025-12-06 The All-in-One Video Gallery plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the resolve_import_directory() function in version…
CVE-2025-12957 HIGH 8.8 2026-01-16 The All-in-One Video Gallery plugin for WordPress is vulnerable to arbitrary file upload in all versions up to, and including, 4.5.7. This is due to insufficient file type validat…
CVE-2020-11026 HIGH 8.7 2020-04-30 In affected versions of WordPress, files with a specially crafted name when uploaded to the Media section can lead to script execution upon accessing the file. This requires an au…
Full Report Available

All 156 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.5?

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.5 is no longer safe for any website, regardless of size or purpose. With 156 known vulnerabilities—including 6 critical ones that allow remote code execution—continuing to run this version is like leaving your front door unlocked. The longer you wait to update, the higher your risk of being compromised, losing customer data, or having your site used to attack others.

Don't leave your WordPress security to chance. Use SiteRecipe.com's vulnerability scanner to instantly identify all CVEs affecting your website, get personalized update recommendations, and receive step-by-step guidance to secure your installation. Our platform takes the guesswork out of WordPress security, helping you patch vulnerabilities in minutes rather than hours. Visit SiteRecipe.com today and take control of your site's security—because an ounce of prevention is worth a pound of cure.

Frequently Asked Questions

Is WordPress 4.5 still supported by Automattic?
No. WordPress 4.5 reached end-of-life in December 2016 and has not received security updates since then. Automattic only provides security support for the current version and the two previous major releases. Using WordPress 4.5 means you're running software that hasn't been patched for over 8 years.
Can I update WordPress without losing my content?
Yes, absolutely. WordPress updates are designed to preserve all your content, posts, pages, and media. Always create a backup first as a safety precaution, but the WordPress update process rarely causes data loss. Most issues occur when old plugins aren't compatible with new WordPress versions, which is why you should test updates on a staging environment first.
What happens if I don't update from WordPress 4.5?
Your site becomes increasingly vulnerable to hacking, malware infection, and data theft. Attackers actively exploit known CVEs in outdated WordPress versions. If compromised, your site could be blacklisted by search engines, used to attack other websites, or have sensitive customer data stolen. The financial and reputational damage far exceeds the effort required to update.
How long does it take to update from WordPress 4.5 to the current version?
Most sites can be updated in 30 minutes to 2 hours, depending on the number of plugins and customizations. You'll also need to test that everything works correctly afterward. SiteRecipe.com can help you identify which steps are necessary for your specific setup and provide guidance to minimize downtime.
Will my plugins work after I update WordPress?
Some older plugins may not be compatible with current WordPress versions. This is why you should identify incompatible plugins before updating. Many outdated plugins can be replaced with modern alternatives, or developers may have released newer versions compatible with current WordPress. SiteRecipe.com helps you identify these compatibility issues before updating.

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