Skip to content
Noroxi

WordPress vulnerability scannerFind known vulnerabilitiesin your WordPress site

Enter a domain: we find the WordPress version, plugins and themes, match them against known vulnerabilities and tell you what to fix first. Nothing is installed on the site.

Scan depth

  • Core, plugin and theme versions
  • Common misconfigurations
  • At most 13 read-only requests

Read-only requests, no password guessing · 3 scans a day without an account · the report opens on its own page

Checking whether your site was hacked? external hack check and first aid

What the report showsfictional domain and plugins

When the scan finishes the report opens at this address; only you know the link. Download it as PDF, Markdown or JSON.

plugins
14,430
themes
1,571
mapped vulnerability records
39,714
records with public exploit code
2,024

Directory updated hourly · newest record Nov 19, 2026

98% of the 38,475 valid WordPress records published by Wordfence, Patchstack and WPScan are linked to a plugin or theme (measured Nov 19, 2026).

How it works

A scan does three things. Then we answer three questions for every vulnerability: a count alone sets no priority.

  1. Finds components

    Extracts the running plugins, theme and core version from the homepage and the REST API. A handful of read-only requests; no password guessing, nothing changed.

  2. Matches vulnerabilities

    Compares every component with our WordPress vulnerability directory. When the version is readable, only records affecting that version count as “confirmed”; otherwise they are “possible”.

  3. Puts them in order

    Vulnerabilities that are actively exploited, need no login or have a ready-made attack tool come first; it names the version to upgrade to and how to close each setting. For a plugin with no fix or one that was closed, it does not say “update”.

Which vulnerability should you fix first?

What we check

The light scan is open to everyone. The deep scan also probes sensitive file paths; it is on paid plans (not during the agency trial) and runs after you confirm you are authorized to scan.

Light scan

10 checks · up to 13 requests

  • Core version

    The version is matched against WordPress core vulnerabilities, branch by branch.

  • Plugins and their versions

    Every plugin brings its own vulnerabilities; a readable version makes the match exact.

  • Themes

    The active theme and child theme are matched against the same directory.

  • wordpress.org status

    Was the plugin removed from the directory, is the installed version behind the latest, does WordPress.org mark the core version as insecure?

  • HTTPS redirect

    A site left on HTTP carries session cookies and passwords in clear text.

  • Username exposure (REST API and author archive)

    Leaked usernames make password-guessing attacks easier.

  • User registration

    With open registration, plugin flaws that need a “subscriber” become exploitable from outside.

  • XML-RPC

    Allows many password guesses per request and pingback abuse.

  • readme.html

    A leftover install file that tells what the site runs.

  • Directory listing (uploads, plugins, themes)

    Every uploaded file can be browsed without guessing URLs; if the plugin/theme folder is listed, the names in it enter the report as components without a version.

Deep scan adds

+7 checks · up to 64 requests

  • Pinning plugin and theme versions

    readme.txt and style.css are read; “possible” records become “confirmed” or “clean”.

  • wp-config backups

    Can the database password and secret keys be downloaded?

  • debug.log

    Contains file paths, queries and sometimes personal data.

  • Database backup and backup folders

    All content and user password hashes; are backup-plugin folders listed?

  • .env and .git

    Can passwords, API keys and source code be downloaded?

  • Install wizard (install.php)

    On an unfinished installation anyone can create an admin account.

  • wp-cron.php access

    Externally triggered scheduled jobs can strain the server (informational, not scored).

The deep scan is on paid plans. No account: create a free account · free plan: see the plans

The light scan requests at most 13 URLs, the deep scan at most 64. All of them are read-only (GET) requests; the content of a sensitive file is never stored, only its path appears in the report.

Noroxi Connector: the full version list from inside your site

The light scan sees what the site shows; plugins that leave no trace on the front end and hidden versions stay “possible”. The free, read-only Noroxi Connector plugin reports from inside your site once a day.

  • Exact version of every installed plugin, theme and core
  • File integrity against WordPress.org's official checksums (paths only, no contents)
  • The PHP version and four settings you cannot see from outside
  • New vulnerability records are matched in the hourly update; you are notified on a match

Who it is for

  • Site owner

    Am I safe, and what should I do?

    • A plain to-do list, ordered by urgency
    • The version to upgrade to for each plugin
    • A “how to fix” note for every setting
  • Agencies and freelancers

    All client sites in one place

    • Shareable report link: send it straight to the client
    • Continuous watching: 1 site on the free account, 20 on Pro, 100 on Agency 100
    • Check a plugin in the directory before installing: closed? fix available?
    • Subscribe to the RSS feed of the plugins you use
  • Security team

    Record data and evidence

    • CVE ID, CVSS, CISA KEV, exploit status (PoC or ready-made tool) and required access level on every record
    • “Confirmed” and “possible” are counted separately; possible records never affect the score
    • Requests identify as NoroxiWP and show up in your logs

Plugin and theme directory

Check before you install: every plugin and theme's known vulnerabilities, active exploitation and patched version.

Ready-made lists6,236 closed plugins965 plugins with no fix seen19,492 records need no login

Highest-risk plugins

All plugins

Highest-risk themes

All themes

Open data and feeds

  • RSS feed

    Newest plugin and theme vulnerabilities; each item carries the component, severity, required access and fix status. Add ?access=unauth for login-free issues only; per-plugin feeds are on each component page.

    Open the feed

  • JSON feed

    The same content for machines. No key needed; responses are cached for 15 minutes.

    Open the JSON

  • Component lookup (API and MCP)

    “Is this version of this plugin affected, who can exploit it, was the plugin closed?” With a free API key or the MCP tool; no scan is run.

    API docs

  • Full directory

    Daily dump: component-to-CVE mapping, access level, fixed version and wordpress.org status. CSV and Parquet.

    Open data

Fields derived by Noroxi are CC BY 4.0. No output contains exploit code or links to it.

What is free, what paid plans add

Scanning, reports and the directory are free. Paid plans add the deep scan, daily re-scans and more sites.

Scan quotaFree account10 per hourPro$29/mo60 per hourAgency 100$99/mo200 per hour
Deep scan (version pinning and sensitive file checks)Free account—Pro$29/moincludedAgency 100$99/moincluded
Re-scan of watched sitesFree accountweeklyPro$29/modailyAgency 100$99/modaily
Watched sitesFree account1Pro$29/mo20Agency 100$99/mo100
Shareable report and directoryFree accountincludedPro$29/moincludedAgency 100$99/moincluded

Without an account you can still run 3 light scans per day.

See plans

Limits and what we don't do

  • A light scan only sees components the site reveals; plugins that leave no trace on the front end are not listed.
  • Records for a component whose version cannot be read stay “possible” and never affect the score; we do not guess versions.
  • No password guessing, no form submissions, no exploitation attempts. We infer a vulnerability from the version, not by exploiting it.
  • If a firewall returns a challenge page, the report says so; we do not impersonate a browser.
  • Government domains are never scanned in any mode.
  • “No fix seen” is written only when the latest wordpress.org release is also affected; we make no such claim for paid plugins.
  • This is not a penetration test: business logic, authorization and custom-code flaws are out of scope.

Frequently asked

One scan is not enough

New records land in the directory every day; a site that is clean today may not be tomorrow. Scan your site and watch it from the report; we will tell you when its status changes.