Site Security Auditor – Plugin & File Checks
Review plugin updates, detect plugin and theme file changes, and follow a clear WordPress security checklist. No account required.
Solid choice
Site Security Auditor is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 3 weeks ago, and scores 64/100 on our health check.
- Actively developed — last update 3 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Site Security Auditor stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| File Integrity | >100 |
| Plugin Updates | >100 |
| security audit | >100 |
| security checklist | #80 |
| site health | >100 |
About Site Security Auditor
From the official readme · v1.4.0Description
Site Security Auditor gives WordPress administrators a practical security review dashboard. See plugin update information, compare plugin and theme files against a trusted snapshot, and understand which settings deserve attention.
Open Tools → Security Audit to start. Each section explains what it checks, what the result means, and what to do next. It is designed for routine maintenance and investigating unexpected file changes, without automatically editing your site.
What you can do
- Review plugin updates: see available updates, inactive plugins and missing or stale update information. Open the familiar WordPress update screen to take action.
- Compare files: save a trusted SHA-256 baseline, then identify added, modified and removed code files in plugin and theme directories.
- Return to your latest report: the most recent file check stays visible with its timestamp and file count. Simply opening the dashboard does not start another scan.
- Download a file report: export the latest result as JSON to review with your developer or host.
- Follow a plain-language checklist: review HTTPS configuration, dashboard code editing and WordPress debug display, with links to Site Health and official guidance.
- Use a responsive dashboard: clear sections, keyboard-accessible controls and a scrollable plugin table on small screens.
A useful maintenance routine
- Review available updates and take a backup.
- Confirm your files are trustworthy before saving the first baseline.
- Run a comparison after maintenance or when investigating changes.
- Match changed files to intentional updates or edits.
- Replace the baseline only after reviewing and trusting the current files.
A baseline records the current state; it does not prove that state is clean. Keep independent backups and ask a trusted professional about unexplained changes.
Scope and limitations
New baselines cover PHP, PHP7, PHTML, INC, TWIG, JSON, JS and CSS files inside the configured plugin directory and registered theme directories. WordPress core, uploads, must-use plugins, database content and other file types are excluded. Symbolic links are not followed and cause an incomplete result.
Each run is bounded to 20,000 directory entries, 100 MiB of file data, 8 MiB per file and an approximately 8-second processing budget. Unreadable files or exceeded limits produce an incomplete report. Incomplete scans never replace a baseline or present a partial comparison as complete. Large sites may need a host-level integrity tool. Avoid editing files or running updates during a scan.
This plugin is not a malware scanner, firewall or vulnerability database. It does not repair files, guarantee security, or certify a plugin as safe. An update or legitimate edit can change a file; unchanged files can still contain problems.
Privacy and performance
No account, API key, telemetry or additional remote metadata requests are required. The dashboard uses the update information already maintained by WordPress; WordPress itself may contact its normal update services.
File hashes, relative paths, baseline time and the latest file report are stored in the site’s options, without autoloading them. Reports are restricted to administrators; on multisite they require a network administrator. Downloaded reports contain relative file paths, so share them only with trusted people. Deactivation and deletion preserve these records to avoid silently discarding your trusted reference.
Installation
- Install Site Security Auditor from Plugins → Add New, or upload the plugin ZIP.
- Activate the plugin.
- Open Tools → Security Audit using an administrator account.
- Read the baseline warning, confirm that you trust the current files, and choose Save trusted baseline.
- Return and select Compare files now to review changes.
On multisite, a network administrator can open the dashboard from a site’s Tools menu. Baselines and reports are stored per site, while plugin and theme files may be shared across the network.
Changelog
New dashboard and safer file checks. Existing baselines remain intact; newly saved baselines also include JS and CSS. Review changes before replacing a baseline.
1.4.0
- New responsive dashboard, guided baseline workflow and actionable security checklist.
- Save the latest file report and download it as JSON.
- Run scans only through authenticated, nonce-protected POST actions.
- Preserve baselines when scans are incomplete; add resource limits and explicit coverage warnings.
- Include JS and CSS in new baselines while preserving legacy comparison scope.
- Use cached WordPress update data instead of per-plugin remote lookups on dashboard views.
- Recognize network-active plugins and restrict multisite access to network administrators.
- Refresh directory branding, documentation, screenshots and release metadata.
1.0
- Initial dashboard for plugin information, file baselines and hardening checks.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Site Security Auditor alternatives
All File Integrity plugins →FAQ
Site Security Auditor: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is Site Security Auditor free?
Yes. Site Security Auditor is free to download and use from the official WordPress.org plugin directory.
Is Site Security Auditor safe to use in 2026?
Site Security Auditor is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 3 weeks ago, and scores 64/100 on our health check.
How many websites use Site Security Auditor?
Site Security Auditor is active on <10 WordPress websites and has been downloaded 1,596 times since it launched in September 2025. It was downloaded 145 times in the last 30 days.
Does Site Security Auditor work with WordPress 7.1?
Yes. The developer has tested Site Security Auditor up to WordPress 7.1.5, the latest release. It requires WordPress 5.8 or newer.
What PHP version does Site Security Auditor need?
Site Security Auditor requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Site Security Auditor last updated?
The latest version, 1.4.0, was released on November 2, 2026 (3 weeks ago).
Who makes Site Security Auditor?
Site Security Auditor is developed and maintained by Gopal Bogati.
What are the best alternatives to Site Security Auditor?
The most popular alternatives to Site Security Auditor are Guardian Gaze Security (40+ installs), INI Protector (30+ installs) and File Change Monitor (30+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card



