Short answer: Site AI Audit reads the headers and the page source that your server sends to everyone, and flags software versions that are announced in them. A server that reveals its version, a visible PHP version and a visible WordPress version are notices. A PHP version below 8.2 is raised to a warning, because that version no longer receives security fixes. Hiding version numbers is cheap, but the real protection is keeping the software up to date.
Why version numbers matter to attackers
Most attacks on websites are not aimed at one particular business. They are automated: a program scans thousands of addresses, looks for software with a known weakness and tries a ready-made attack against every match. The first step of that scan is finding out what the site runs. If your server announces “version 2.4.41” or your page source says “WordPress 5.8”, the scanner does not have to guess. It knows which known problems apply and can go straight to the attack.
Hiding the version is therefore not a magic shield, but it removes a free hint. The audit’s explanation says that version numbers help attackers find known vulnerabilities. That is why the findings exist, even though they are only notices: they reduce the amount of information that a stranger gets for nothing.
The findings in this group
Three findings in the security area deal with versions:
- The server reveals its software version (notice). The Server header contains a version number, such as a web server name followed by a slash and digits. The advice is to hide version details in the Server header.
- The server reveals its PHP version, or the site runs an outdated PHP version. If the X-Powered-By header or another sign shows the PHP version, the audit reports a notice. If that version is below 8.2, the finding becomes a warning with the title “The site runs an outdated PHP version”, because versions below 8.2 no longer receive security fixes. The advice is to upgrade PHP to a supported version and to hide X-Powered-By, or to turn off expose_php.
- WordPress version N is publicly visible (notice). The page source includes the WordPress version, usually in a generator tag. The advice is to remove the generator tag and to keep WordPress, themes and plugins updated.
Only the finding that applies to your site is shown. A site that does not use PHP or WordPress will not see those findings.
Hiding versus updating
It helps to be clear about priorities. Hiding a version number tells strangers less. Updating the software removes the weakness itself. If you have to choose, always update first. A site on an old PHP version with the number hidden is still a site on an old PHP version, and a determined attacker will test it anyway. The hidden number only slows down the lazy ones.
The outdated PHP finding shows this well. It is the only one in the group that is a warning, because the risk is real and not just informational: PHP versions below 8.2 no longer get security fixes, so any newly discovered weakness stays open. Upgrading has side benefits too. Newer PHP versions are noticeably faster, which is explained in the article on why upgrading PHP makes your website faster and safer.
How to hide the server version
The method depends on your server:
- Apache. Set the ServerTokens directive to Prod, and ServerSignature to Off.
- Nginx. Set server_tokens to off.
- Managed hosting. You may not be able to change it. Ask your host whether they can hide the version, or accept the notice if they cannot.
- A CDN or proxy in front of the site. Many replace the Server header with their own name, which clears the notice automatically.
A related header is X-Powered-By, which often reveals the PHP version. In php.ini you can set expose_php to Off, and a hosting panel usually has a switch for it.
How to hide the WordPress version
WordPress adds a generator tag to the head of every page, and it also appends the version to the address of some scripts and styles. To remove them:
- Update WordPress, themes and plugins first, so that you are on a current version when the number is visible anyway.
- Remove the generator tag with a small code snippet or a security plugin that has the option.
- Consider removing version query strings from scripts and styles. This also helps caching in some setups.
- Check the page source afterwards. Search for “generator” and for the old version number.
- Run the audit again to confirm that the notice is gone.
The guide to a safe update strategy for outdated plugins and CMS versions shows how to update without breaking the site: back up, update on a copy if you can and do the riskiest updates first.
The bigger picture: patching
Because version flags are about known weaknesses, the best response is a routine for updates. That means someone is responsible for updating WordPress, themes and plugins every few weeks, removing plugins that are no longer maintained and checking that the host keeps PHP current. The article on abandoned WordPress plugins explains why old plugins are the most common way in. If an urgent update is impossible, a stopgap is described in virtual patching, which blocks a known attack before you can install the real fix.
Check what your site announces today
You can look at the headers yourself in a minute. Open your site in a browser, open the developer tools, choose the network tab, reload and click the first request. In the response headers, look for a Server line with a number after a slash, and for X-Powered-By. Then view the page source and search for “generator”. Whatever you find there, a stranger can read too. If your host controls the headers, take a screenshot and send it with your request, so that support can see exactly which lines you want removed.
Keep a simple update log
Version findings are really questions about housekeeping: who updates what, and when? A short log is enough: the date, what was updated, from which version to which, and whether anything broke. It takes a minute per update and is worth a great deal when something goes wrong, because it tells you what changed last. It also turns the next audit into a quick confirmation instead of a surprise. If several people look after the site, the log prevents two of them from updating the same thing on different days and arguing about the result.
What about themes and plugins that name themselves?
Besides the generator tag, many themes and plugins add their own name and version to the page source in comments and in the addresses of their style sheets and scripts. These are harder to hide completely, and it is not worth hunting for every one. A better use of your time is to remove the plugins and themes that you do not use at all, because an inactive plugin can still contain a weakness that attackers can reach. Delete what you do not need, update what remains and treat the version notices as a prompt to review the whole list.
A worked example
A small manufacturing company has a WordPress site that was built three years ago. The audit shows three findings in the security area: a warning that the site runs PHP 7.4, a notice that WordPress 5.9 is visible, and a notice that the server reveals its version. The IT contractor asks the host to move the site to PHP 8.3, first testing it on a copy because one old plugin throws an error. He replaces that plugin, updates WordPress and the other plugins, removes the generator tag and asks the host to hide the server version. A new check shows no version findings. The site is also faster, and the contractor writes down the dates of the updates in a short log for the next time.
To find out what your own site announces, check your website with Site AI Audit. The check needs a free account; the plans unlock the full report with the exact findings.
Related reading
- Plugin Supply Chain Attacks: When a Trusted Update Turns Bad
- WordPress User Enumeration: What It Reveals and How to Stop It
- WordPress xmlrpc.php: What It Does and When to Disable It
- Is Your Website Protected From Hacking? What the Audit Checks
The bottom line
Visible version numbers give attackers a free map. Hide them where you can, but spend most of your effort on updating PHP, WordPress and plugins. Run the audit again after the changes to see that the notices have gone.
KKK
Is hiding the version enough to be secure?
No. It removes a hint, but the weakness remains until you update. Treat hiding as a small extra step.
Why is the PHP finding a warning when the others are notices?
PHP versions below 8.2 no longer receive security fixes, so the risk is real. The other findings only reveal information.
Can I hide the WordPress version without a plugin?
Yes. A short snippet in your theme’s functions file can remove the generator tag. A security plugin can do the same with a setting.
Will the audit see the version if I hide it in the page but not in the headers?
It checks both. Remove the generator tag and the version query strings, and hide the headers on the server.
What if my host does not let me change these settings?
Ask the host. If they cannot, focus on updates and consider a CDN, which often replaces the Server header.



