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

WordPress 4.6.1 Security: 38 CVEs Explained & How to Fix

📅 June 07, 2026 ·⏱ 5 min read ·🔒 SiteRecipe Security Team
115 websites still running wordpress 4.6.1  → View full list
38
Total
3
Critical
7
High
26
Medium
2
Low

WordPress 4.6.1 is an outdated version with significant security vulnerabilities that put your website at serious risk. Our analysis found 38 confirmed CVEs affecting this version, including 3 critical vulnerabilities that could allow attackers to take complete control of your site. If your website is still running this older version, you're exposed to remote code execution, SQL injection, and file inclusion attacks that hackers actively exploit.

With 115 websites still using WordPress 4.6.1, this is a widespread security concern. The vulnerabilities are well-documented and easily exploitable, making your site an attractive target. This guide will help you identify if you're vulnerable and walk you through the steps to secure your WordPress installation immediately.

What is Wordpress 4.6.1?

WordPress 4.6.1 was released in 2016 as a minor security update to the WordPress content management system. It's the software that powers over 43% of all websites on the internet. Think of WordPress as the foundation of your website—it manages your content, handles user access, and connects all your plugins and themes together. When your WordPress version becomes outdated, it's like leaving your front door unlocked while security flaws are publicly known.

This version is now over 8 years old and has been superseded by dozens of updates. WordPress regularly releases security patches to fix vulnerabilities, but these only work if you're running a current version. Running WordPress 4.6.1 means you're missing years of security improvements and bug fixes. Even worse, the plugins you use on this old version likely have their own vulnerabilities, creating multiple layers of risk that attackers can exploit.

Key Vulnerabilities in Wordpress 4.6.1

38 CVEs found. The most critical are explained below.

CRITICAL CVE-2024-6386 9.9/10 · CVSS v3.1 ⏱ Immediate
WPML Plugin Allows Hackers to Take Over Your Site

The WPML plugin has a serious flaw that lets attackers with login access run malicious code on your website. This happens because the plugin doesn't properly check what users are entering into certain forms.

Impact: An attacker could take complete control of your website, steal customer data, install malware, or shut down your site entirely.

↗ View on NVD
CRITICAL CVE-2015-9452 9.8/10 · CVSS v3.1 ⏱ Immediate
Nex Forms Plugin Exposes Database to Attack

The Nex Forms plugin contains a SQL injection vulnerability that allows attackers to directly access your website's database without proper authentication. This happens because the plugin accepts user input without validating it first.

Impact: Hackers could steal sensitive information like customer names, emails, and passwords, or modify/delete critical business data.

↗ View on NVD
CRITICAL CVE-2024-4098 9.8/10 · CVSS v3.1 ⏱ Immediate
Shariff Plugin Lets Anyone Run Code on Your Server

The Shariff Wrapper plugin has a flaw that allows anyone (even without a login) to access files on your server and run code. An attacker can use this to install backdoors or steal your data.

Impact: Your entire website and server could be compromised, potentially affecting all customer data and website functionality.

↗ View on NVD
HIGH CVE-2019-14788 8.8/10 · CVSS v3.1 ⏱ Immediate
Tribulant Newsletters Plugin Security Breach

The Tribulant Newsletters plugin allows attackers to access files outside their intended directories and execute code on your server. This happens through a path traversal vulnerability in the export function.

Impact: Attackers could access confidential files, install malware, steal subscriber lists, or gain full control of your website.

↗ View on NVD
HIGH CVE-2017-18523 8.8/10 · CVSS v3.0 ⏱ Within 7 days
Eelv Newsletter Plugin Address Book Can Be Hijacked

The eelv-newsletter plugin is missing protection against CSRF attacks, which means attackers can trick logged-in users into performing unwanted actions like modifying address books without their knowledge.

Impact: Your mailing lists and subscriber data could be altered or deleted by attackers impersonating legitimate users.

↗ View on NVD
HIGH CVE-2023-5931 8.8/10 · CVSS v3.1 ⏱ Within 7 days
rtMedia Plugin Allows Malicious File Uploads

The rtMedia plugin doesn't properly check files before allowing them to be uploaded. This means even low-level users can upload dangerous files like PHP scripts that can execute code on your server.

Impact: Attackers could upload and run malicious code to compromise your website, steal data, or disrupt your services.

↗ View on NVD

Additional Vulnerabilities (32 more)

Showing first 10 of 32. View all on NVD ↗

CVE IDSeverityScore PublishedDescription
CVE-2024-3293 HIGH 8.8 2024-04-23 The rtMedia for WordPress, BuddyPress and bbPress plugin for WordPress is vulnerable to blind SQL Injection via the rtmedia_gallery shortcode in all versions up to, and including,…
CVE-2024-2386 HIGH 8.8 2024-06-29 The WordPress Plugin for Google Maps – WP MAPS plugin for WordPress is vulnerable to SQL Injection via the 'id' parameter of the 'put_wpgm' shortcode in all versions up to, and in…
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…
CVE-2023-5939 HIGH 7.2 2023-12-26 The rtMedia for WordPress, BuddyPress and bbPress WordPress plugin before 4.6.16 loads the contents of the import file in an unsafe manner, leading to remote code execution by pri…
CVE-2020-4047 MEDIUM 6.8 2020-06-12 In affected versions of WordPress, authenticated users with upload permissions (like authors) are able to inject JavaScript into some media file attachment pages in a certain way.…
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-2024-1450 MEDIUM 6.4 2024-03-21 The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'shariff' shortcode in all versions up to, and including, 4.6.10 due to insu…
CVE-2024-2695 MEDIUM 6.4 2024-06-15 The Shariff Wrapper plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'shariff' shortcode in all versions up to, and including, 4.6.13 due to insu…
CVE-2025-4594 MEDIUM 6.4 2025-05-23 The Tournamatch plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'trn-ladder-registration-button' shortcode in all versions up to, and including,…
CVE-2016-7169 MEDIUM 6.3 2017-01-05 Directory traversal vulnerability in the File_Upload_Upgrader class in wp-admin/includes/class-file-upload-upgrader.php in the upgrade package uploader in WordPress before 4.6.1 a…
Full Report Available

All 38 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.6.1?

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

Securing WordPress 4.6.1 isn't optional—it's essential for protecting your website, your users' data, and your business reputation. The 3 critical vulnerabilities we identified can give attackers complete control of your site, allowing them to steal data, inject malware, or use your server for criminal purposes. By updating to the latest WordPress version and patching all vulnerable plugins, you eliminate the vast majority of these risks.

Don't wait until your site is compromised. SiteRecipe.com provides fast, comprehensive vulnerability scanning that instantly identifies which CVEs affect your WordPress installation and recommends specific fixes. Start your free security scan today and take control of your website's safety. Your future self will thank you when you're not dealing with a hacked site or data breach.

Frequently Asked Questions

Is WordPress 4.6.1 still supported with security updates?
No, WordPress 4.6.1 reached end-of-life years ago and receives no security patches whatsoever. WordPress only supports the current version and a few recent releases. Staying on 4.6.1 means you're completely unprotected against newly discovered vulnerabilities.
Will updating WordPress break my website or plugins?
Updating can sometimes cause compatibility issues, but this is rare with modern hosting. That's why backing up first is crucial. Most reputable plugins and themes maintain compatibility across WordPress versions. SiteRecipe.com can identify potential compatibility issues before you update.
What's the fastest way to find all vulnerabilities affecting my WordPress site?
SiteRecipe.com's automated security scanner analyzes your WordPress version, all plugins, and themes against the latest CVE database in seconds. It provides a detailed report showing exactly which vulnerabilities affect your site and how to fix each one.
Can attackers really exploit WordPress 4.6.1 vulnerabilities remotely?
Yes, several CVEs including CVE-2024-6386 (Remote Code Execution) and CVE-2015-9452 (SQL Injection) allow unauthenticated attackers to compromise your site without any direct access. They can exploit these vulnerabilities from anywhere on the internet.
How long does it take to update from WordPress 4.6.1 to the latest version?
The actual update process takes 5-10 minutes, but you should allocate 30-60 minutes total to backup your site, perform the update, and verify everything works correctly. SiteRecipe.com can guide you through the process step-by-step.

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