Contents
- 1What WordPress checks, not antivirus
- 2Where WordPress gives too many capabilities if you do not restrict them
- 3What the risks mean according to OWASP
- 4A practical set of checks worth doing today
- 5Why the convenient habit of “checking your computer” is not the same as site security
- 6Frequently asked questions
The idea that “we have antivirus, so the site is safe” sounds reassuring, but for WordPress it is not enough. Antivirus protects the computer on which it is installed. Website security, however, depends on very different things: the WordPress version, the state of plugins and themes, server settings, the PHP version, file system permissions, and whether file editing is allowed directly from the admin panel.
That is why it is better to think in terms of several layers rather than one “protection tool.” A WordPress site lives on a server, interacts with a database, processes HTTP requests, executes PHP code, and depends on which files can be changed and which cannot. If even one of these layers is configured weakly, antivirus on an employee’s laptop will not notice it.
Key takeaways
- Antivirus protects your computer; the site runs on a server.
- Sites get hacked through vulnerable plugins, weak passwords and misconfiguration.
- Site security comes from updates, access control and backups.
What WordPress checks, not antivirus
WordPress has a Site Health tool that shows the site’s status and a list of specific checks. It does not look at the “overall configuration” in the abstract, but at clearly defined parameters: the current WordPress version, active and inactive plugins and themes, the database, the server environment, and file system permissions.
In the server section of Site Health, you can see, among other things, the server architecture, web server type, PHP variables, maximum execution time, maximum upload size, the cURL version, SUHOSIN, Imagick, pretty permalinks, and .htaccess rules. In the file permissions section, WordPress directly reports whether it can write to the necessary directories: the main WordPress directory, wp-content, uploads, plugins, and themes.
This matters in practical terms: antivirus on a PC does not have access to this range of checks. It will not tell you that the server has overly permissive write access, it will not show an inappropriate PHP setting, and it will not assess whether WordPress’s own file directories are working correctly.
Another detail that is often overlooked
The Site Health screen is informational. It shows the current state, but it does not change settings by itself. In other words, it is useful as diagnostics, but not as a mechanism for fixing problems. This is a good example of why a site needs separate technical attention rather than just “user computer protection.”
Where WordPress gives too many capabilities if you do not restrict them
The official WordPress documentation states directly that the admin dashboard allows PHP files for plugins and themes to be edited by default. That is convenient for a developer, but risky for security and stability. For this reason, WordPress recommends disabling file editing if the built-in editor is not needed, using DISALLOW_FILE_EDIT.
There is also a broader restriction: if you set DISALLOW_FILE_MODS, plugin and theme installation and updates are disabled in the admin panel, along with the file editor for plugins and themes. This is not a minor cosmetic change, but control over whether someone can modify code from the dashboard.
It is important not to mix everything into one paragraph. File editing, permission to modify directories, the behavior of wp-config.php, and access to updates are different things. It is useful to consider them separately, because each one closes its own risk.
wp-config.php as an example of targeted hardening
WordPress recommends keeping wp-config.php one level above the WordPress installation, that is, outside the web root, and restricting access to it to you and the web server only. The documentation lists the typical permissions 400 or 440.
This is not a universal recipe for every case, but it is a very telling example: site security often depends not on an “antivirus signature,” but on whether a third-party process can read or modify a critical configuration file.
What the risks mean according to OWASP
In its introduction, OWASP Top 10: 2025 names separate risk categories: Broken Access Control, Security Misconfiguration, Software Supply Chain Failures, Injection, Authentication Failures, Software or Data Integrity Failures, Security Logging & Alerting Failures, and Mishandling of Exceptional Conditions.
This list is important not as a collection of scary terms, but as a reminder that danger to a site does not come only from a malicious file on a computer. It also arises from incorrect access permissions, configuration errors, software supply chain issues, authentication problems, injection, and weak logging and alerting for incidents.
Good logging by itself is of little use if no one receives a notification about the event in time. OWASP explicitly highlights this difference.
For WordPress, this means something simple: security should not be reduced to “do we have antivirus?” You need to check who has access to the admin panel, whether components are up to date, whether the file system allows too much, and whether there is any mechanism at all that will notify you about suspicious activity.
A 15-minute security check
- Are core, theme and plugins up to date?
- Are only the people who need it administrators?
- Is two-factor authentication on for admins?
- Is there a fresh backup off the site's server?
A practical set of checks worth doing today
If you look at a site without marketing simplifications, the basic checklist looks like this:
- make sure WordPress, plugins, and themes are updated;
- check which plugins are active and which are not;
- review the PHP version and key server parameters in Site Health;
- check permissions for
wp-content,uploads,plugins, andthemes; - restrict or disable file editing from the admin area if it is not needed;
- check where
wp-config.phpis located and who can read it; - make sure backups exist and that restore testing has been performed;
- check whether there is login and event logging, as well as alerts for suspicious changes.
It is especially useful to review the list of administrators, hosting access, DNS, and email separately. Compromise of any of these layers can change the site’s behavior even when everything looks “clean” on the work computer.
Why the convenient habit of “checking your computer” is not the same as site security
Antivirus does not see whether a plugin has overly broad permissions on the server. It will not show that PHP file editing is available in the admin panel. It will not assess whether wp-config.php is properly protected, whether .htaccess rules are working, whether write directories are configured correctly, or whether notifications about suspicious actions arrive in time.
In other words, computer protection and WordPress site protection exist on different levels. The first reduces the risk of infection on the user’s side. The second requires control over code, roles, access, files, updates, and the server environment. That is where real WordPress hygiene begins.
So it is more useful to ask not “do we have antivirus?” but instead: can we see the state of WordPress, are dangerous actions in the admin area restricted, are critical files protected, are components updated, and is there a way to notice an incident quickly before it turns into a problem for the whole site?
Read also: “WordPress Backup Strategy: How to Maintain Business Continuity During Technical Failures” and “Why nulled WordPress themes create a risk of data loss, even if the site “works normally””.
Frequently asked questions
Why doesn't antivirus protect a WordPress site?
Antivirus scans your computer, while the site runs on a server. It can't see vulnerable plugins, weak admin passwords or configuration mistakes.
What should be checked on the site first?
Core, theme and plugin updates, the list of administrators, two-factor authentication, the Site Health report and recent backups.
Which risks most often lead to a hack?
Following OWASP: broken access control, security misconfiguration and vulnerable components such as outdated plugins and themes.