Here, we’ll explain how to monitor and respond to WordPress vulnerability information within your organization.
Tag: WordPress plugin Page 1/15
We’ll explain typical patterns of malicious code embedded in WordPress’s `wp_posts` and `wp_options` tables as a result of malware infection, as well as how to distinguish it from legitimate code. Malware Infection and Tampering of the WordPress Database In the event of a malware
Here’s how to prevent site-wide warning messages caused by failed automatic renewals of free SSL (Let’s Encrypt).
I’d like to discuss the issue that security measures for many WordPress sites tend to focus too much on protecting the login process.
Here’s a guide on how to regain administrator privileges after the person in charge of your WordPress site—which you had outsourced to a production company—has resigned or gone out of business.
The site looks normal, but search results are flooded with product pages or appear in Chinese—here’s an explanation of how to detect and completely remove SEO spam.
Slider Revolution (RevSlider) case study will explain the risks of “plug-ins that are out of license or have been moved to paid” and how to deal with vulnerabilities of such plug-ins.
We will explain how to identify and deal with the three causes of WordPress malware that can resurface after a certain period of time even if it is removed: malicious processes, mu-plugins, and hidden administrators.
We will explain how to use a security plugin to automatically prevent WordPress htaccess and index.php from being rewritten by malware.
WordFence says “no problem” even though the site is infected with malware, and Google Search Console is giving a malware warning. Or conversely, we will explain the discrepancy where WordFence detects malware and Search Console and Safe Browsing show no problem.
We will explain the latest password policy (how to determine a unified password) when using WordPress with multiple administrators and editors (contributors).
We will explain why plug-ins can be compromised even if they are up-to-date – vulnerabilities created by “obsolete plug-ins” based on the attack patterns we have detected.
This section explains what to do if you have installed 2FA or other security plugins for WordPress and can no longer log in yourself.
We will explain actual cases of WordPress plug-ins becoming malware due to acquisition by another company or hijacking of wordpress.org accounts, and how to prevent this from happening in advance.
There are cases where WordPress is infected with malware even though WordPress itself and all plugins are up-to-date. We will explain the real route of entry in this case.
Here is a simple PHP code (in functions.php) that detects a brute force attack on wordpress and blocks that IP for 1 hour.
We will explain why you may not notice that your WordPress site has been tampered with and how to create a mechanism for early detection.
A brute force attack may be the cause of the frequent 504 and 403 errors on your WordPress site. We will explain the symptoms and how to deal with this issue.
