WP Advanced Security By WooNinjas is a WordPress plugin that checks your site for security risks and shows you exactly where they are. It scans your codebase for SQL injection, XSS, CSRF, remote code execution, and runtime PHP errors, and points you to the exact file and line for each issue.
The plugin also monitors incoming traffic, checks your site against global blacklists, verifies your WordPress core files, and gives you a list of security recommendations to fix. Everything shows on one dashboard, so you can see your site’s security health at a glance.
This article covers how to set up the plugin, read the Overview dashboard, run a deep scan, and review your findings.
Installation
- Install the WP Advanced Security by WooNinja plugin & activate it.
- After activation, the “WP Security” menu will appear in your dashboard.
- The menu has two pages: “Overview” and “Vulnerability Scanner.”
- Go to the Vulnerability Scanner page and click on “Run Deep Scan” to run your first scan.

Overview
The Overview tab gives you a real-time view of your site’s health status, codebase vulnerability metrics, and runtime diagnostics.

Security Issues Banner
Shows at the top of the page when the plugin finds security issues. It shows the total number of active vulnerabilities detected across your site. Click on “Go to Vulnerability Scanner” to see the full list of issues.
Overview, Documentation & Support
Use the links at the top right of the Overview section to open the Overview, read the plugin documentation, or click on “Open a Support Ticket” to contact the WooNinjas support team.
Note: The Overview and Vulnerability Scanner tabs are available at the top of both plugin pages, so you can switch between them anytime.
Server Environment
This bar shows the main details of your server setup:
- PHP Version: the PHP version your site runs on.
- WordPress: your current WordPress version.
- Web Server: your web server software and version (e.g., Apache).
- MySQL: your database server version.
- Memory Limit: the PHP memory available to your site. An “Available” badge shows when the limit is healthy.
WAF Traffic & Exploit Attempts
This chart shows incoming request filtering and threat defense for the last 24 hours. The Y-axis shows the number of requests, and the X-axis shows the timeline in UTC.
- Sanitized Requests: requests the firewall checked and cleaned before they reached your site.
- Blocked Threats: requests the firewall blocked as exploit attempts.
- Total Traffic Analyzed: the total number of requests checked in the last 24 hours.
Hardening Index
The Hardening Index is your site’s overall security score as a percentage. A low score shows a “Critical Attention” status, which means your site needs fixes right away. Fix the issues in the Security Status, Blacklist & Threat Checks, and Security Recommendations sections to raise your score.
Security Status
Below the chart, three cards show your site’s security checks and what to fix next.


The Security Status card runs a structural static analysis of your codebase. Each check shows a green tick when it passes, or a red cross with the number of issues found.
No Dynamic SQL Injection Sinks
Checks for database queries built from unsafe input that could allow SQL injection.
No Unescaped Superglobal Echoes (XSS)
Checks for code that prints user input (like $_GET or $_POST) to the page without escaping it, which could allow cross-site scripting (XSS).
No Insecure Deserialization Calls
Checks for unserialize() calls on untrusted data, which could allow PHP object injection.
No eval() Remote Code Execution Sinks
Checks for eval() and similar calls that could let an attacker run code on your server.
Uploads Directory Protected
Checks if PHP files are blocked from running inside your uploads folder. An “Unguarded” status means PHP can run there.
Sensitive Files Protected (.env, wp-config)
Checks that sensitive files like .env and wp-config.php can’t be accessed publicly.
The bottom of the card shows how many of the 6 checks have passed. An “Attention” badge shows at the top right when any check fails.
Blacklist & Threat Checks
This card checks your site against global threat databases and verifies your core files.

Google Safe Browsing API
Checks if Google has flagged your site as unsafe. “Verified Clean” means your site isn’t flagged.
WordPress Core Checksums
Compares your WordPress core files with the official WordPress.org versions. It shows the number of deviations found. You can see each one under the Core Integrity filter on the Vulnerability Scanner page.
No Public Root Foreign Scripts
Checks for unknown scripts in your site’s public root folder.
PhishTank Global Database
Checks if your site is listed in the PhishTank phishing database. “Whitelisted” means your site isn’t listed as a phishing site.
Spamhaus IP Reputations
Checks your server’s IP address against Spamhaus blocklists. “Reputable” means your IP isn’t blocklisted.
Runtime Logs Tail Monitored
Monitors your PHP runtime log and shows how many entries are logged. You can see them under the PHP Errors and PHP Warnings filters on the Vulnerability Scanner page.
Security Recommendations
This card lists the fixes your site needs, in order. The badge at the top right shows how many recommendations are pending.

Each recommendation shows the issue title and a short fix. Click on the arrow next to a recommendation to see its full details. The card shows 3 recommendations per page. Use the arrows at the bottom right to move between pages.

Common recommendations include:
- Unwanted / Foreign File in WordPress Root: a file in your root folder isn’t part of WordPress. Review it, and delete it if your site or hosting setup doesn’t need it.
- PHP Execution Allowed in Uploads Directory: PHP files can run inside your uploads folder. Block PHP execution in that folder.
- Local File Inclusion: User Input in include/require: a file path comes from user input. Use a strict allowlist of file names and validate paths with basename() or realpath().
- PHP Object Injection: unserialize() on Untrusted Data: use wp_json_encode() and json_decode() instead of PHP serialization for user data.
Important: Take a full backup of your site before you delete files or change code based on a recommendation.
Vulnerability Scanner
Go to the “Vulnerability Scanner” tab. The scanner audits your codebase for SQL injection, XSS, CSRF, RCE, and runtime PHP errors, and pinpoints the exact file and line for each issue.

Run a Deep Scan
- Go to WP Security ➔ Vulnerability Scanner.
- Click on the “Run Deep Scan” button.
- The scanner starts checking your files and shows a progress bar.
- Wait for the scan to finish. The findings list updates as new issues are found.
While the scan runs, the progress bar shows:
- Scan stage: what the scanner is doing right now (e.g., checking core checksums).
- Progress: the scan progress as a percentage.
- Files audited: the number of files checked out of the total files on your site.
- Issues discovered: the number of issues found so far.
- Current file: the path of the file being scanned right now.
Click on “Cancel Scan” to stop the scan at any time.

Note: A deep scan checks every file on your site, including your plugins and themes. On large sites, the scan can take a few minutes.
Filter Findings
Use the filter tabs above the table to see a specific type of finding. Each tab shows the number of findings in it.
All Findings
Shows every issue the scanner found.
Security Sinks
Shows code patterns that could be exploited, such as SQL injection, XSS, file inclusion, and remote code execution.

PHP Errors
Shows PHP errors from your runtime log. If there are no errors, the table shows “No findings match your filters.”

PHP Warnings
Shows PHP warnings and notices from your runtime log, such as undefined properties. These issues don’t break your site, but they can point to buggy or outdated code.

Core Integrity
Shows files that don’t match the official WordPress core, such as unknown files in your WordPress root folder.

Note: Not every file in Core Integrity is harmful. Some files are added on purpose, such as Google Search Console verification files (e.g., google[code].html). Check each file before you delete it.
Search, Sort & Clear Logs
Search
Search your findings by file name, rule, or issue.
Sort by
Choose how to sort the findings list. You can also click on any column header to sort by it.
Order
Switches the sort order between ascending and descending.
Clear Logs
Clears the current findings list. Run a new deep scan to get fresh results.
Findings Table
Each row in the table shows one issue:
- Severity: how serious the issue is: Critical, Medium, or Low.
- Issue Title & Rule: the name of the issue and the rule it breaks.
- Location: the file name, the line number (e.g., L2), and the file path.
- Category: the issue type, such as File Traversal & LFI, Runtime Diagnostics, or Foreign / Unknown File.
- Action: click on “Inspect” to see more details about the issue.
Note: Many findings come from third-party plugins and themes. Don’t edit those files directly, as your changes will be lost on the next update. Update the plugin or theme to its latest version, or report the issue to its developer.
FAQ’s
1- What does the Hardening Index mean?
It’s your site’s overall security score. A low score means your site has issues that need attention. Fix the failed checks and pending recommendations to raise it.
2- How do I find where an issue is in my code?
Go to the Vulnerability Scanner tab. The Location column shows the file name, line number, and full file path for every issue.
3- How long does a deep scan take?
It depends on how many files your site has. Small sites finish fast, while large sites with many plugins can take a few minutes.
4- Can I stop a scan once it starts?
Yes. Click on the “Cancel Scan” button while the scan is running.
5- Should I delete every file listed under Core Integrity?
No. Review each file first. Some files, like Google Search Console verification files, are added on purpose. Always take a backup before you delete anything.
6- Why are most findings in other plugins?
The scanner checks every file on your site, including third-party plugins and themes. Update those plugins to their latest versions, or report the issue to their developers.
7- How do I get help with a finding?
Click on “Open a Support Ticket” on the Overview tab to contact the WooNinjas support team.
Changelogs
1.0.0
- Initial Release.