These two tools help you find known weaknesses and close simple configuration gaps. Neither changes your files on its own.
Where to find it: ARN SiteWatch → Site Protection → Vulnerabilities and Site Protection → Hardening.

Check for known vulnerabilities
SiteWatch compares the installed versions of WordPress, your plugins and your themes with published advisories from WPVulnerability.
- Open Site Protection → Vulnerabilities.
- Click Refresh vulnerability data. The comparison runs in the background through WordPress scheduled tasks; the screen says when it is queued or in progress.
- When it finishes, Last comparison shows the time, and each component shows its name, version and status.
- Open a component to see each advisory with its Severity, Score, Affected range and advice.
- Use Review published source to read the advisory itself.
| Advice shown | Meaning |
|---|---|
| Review the source for the fixed release, then update and run a health check. | A fixed version is known |
| No fix reported. Review disabling or replacing the affected component. | No fix is known yet |
To compare automatically every day, tick Compare published vulnerability data daily in Monitoring → Site & Asset Health.
Things to keep in mind:
- The check sends plugin and theme slugs and the WordPress version to WPVulnerability. No site content is sent.
- Private and commercial packages may not be in the advisory data. "No information" is not the same as "safe".
- An advisory describes a version concern. It does not prove that your site was attacked.
- An available update and a published vulnerability are separate things; SiteWatch shows them separately.
Apply hardening safeguards
Under Configuration safeguards:
- Tick Disable the built-in plugin and theme file editors to stop anyone from editing code in Appearance and Plugins.
- Tick Hide PHP error output after SiteWatch loads so visitors do not see PHP warnings.
- Click Save safeguards.
Both are off by default; every setup profile turns them on. To undo one, untick it and save. Settings in wp-config.php and hosting rules stay in charge: if wp-config.php already disables the file editor, unticking does not enable it. Errors that happen before plugins load must be hidden in the hosting settings or wp-config.php; error logging can stay on.
The screen also shows the current state of WP_DEBUG, WP_DEBUG_DISPLAY and DISALLOW_FILE_EDIT.
Check exposure and permissions
- Check public access to sensitive files tries to open selected sensitive files from the outside and lists each path with its result and HTTP status.
- Filesystem permissions & root executable review checks eight sensitive paths for world-writable permissions and lists unexpected PHP files in the site's root folder (up to 100 entries).
These checks only read. They do not change permissions or delete files. An unexpected file name is something to review, not proof of an infection. Permissions on Windows servers, file ownership and hosting isolation need a review by your host.