Loading...

WordPress Checker

Discover public WordPress components, compare releases and review known vulnerabilities — no API key required.

Public HTTP/HTTPS URLs only. Queries and fragments are removed. Up to 3 pages and 60 seconds of processing.

Start with a public website URL

Public detection is incomplete. Hidden or inactive components may be missed. Versions are observations; no matching advisory does not guarantee security.

WordPress
—
Themes & plugins detected
—
Updates available
—
Advisory matches
—

Public detection is incomplete. Hidden or inactive components may be missed. Versions are observations; no matching advisory does not guarantee security.

Data sources: WordPress.org · WPVulnerability · CC0 1.0

Follow VuiZ.Net on Google Search

Add VuiZ.Net as a preferred source on Google to find your favorite tools more easily.

  • Find your tools again
  • Discover new utilities
  • Support VuiZ.Net
Follow

Check the WordPress components visible on a website

Enter a public website URL to inspect WordPress signals and the themes and plugins visible in its HTML and assets. VuiZ makes these requests from its server. Query parameters and fragments are removed from the submitted URL.

Latest release metadata comes from WordPress.org. Known vulnerability information comes from the public WPVulnerability API. Neither source requires an API key for these lookups; component metadata is cached for six hours.

Key features

  • Evidence and confidence. Inspect generator tags, theme stylesheet headers, plugin readmes and asset URLs. Estimated or conflicting versions remain distinguishable from stronger evidence.
  • Updates and advisories. Compare detected releases with the official directory and see matching advisories, CVSS scores when available, affected ranges and source links.
  • Public configuration. Review HTTPS, validated TLS connections, selected security headers and HTTP resources referenced by the first HTML page.
  • Portable results. Copy or download the report as JSON, or export a component inventory as CSV.

How to check a WordPress website

Inspect public evidence and prioritize follow-up checks.

  1. Enter the public URL. Paste a domain or HTTP/HTTPS page URL. A domain without a scheme uses HTTPS. Only ports 80 and 443 are accepted.
  2. Start the check. Select Check website and follow the queued, discovery and lookup stages. Reset cancels the current scan.
  3. Inspect components. Open the WordPress, Themes and Plugins tabs. Use the update, alert or unknown-version filter and expand Evidence & details.
  4. Review security findings. Open Security to inspect advisory sources and affected ranges. Confirm uncertain versions on the website before acting.
  5. Export your report. Use Copy JSON, Download JSON or Download CSV to save the results and their verification status.

Usage tips

  • The scan reads up to three HTML pages, twenty components and thirty target requests, within a sixty-second processing budget. Metadata lookups share that time budget. Slow or blocked requests can produce partial results.
  • Only public evidence is inspected. Inactive plugins, hidden components, custom content paths and premium update channels may be absent. No passwords, exploitation or malware inspection are performed.
  • Reports are temporarily stored for thirty minutes and protected by a per-scan token. Save an export before leaving the page. A current version or an empty advisory list is not a guarantee of security.

Frequently asked questions

No. It detects components referenced by the inspected public pages and reads their public metadata. Plugins with no frontend footprint and inactive components may be invisible.
Asset query strings may be cache tokens or WordPress versions. A plugin readme may be stale. The checker records these candidates and treats unsupported or conflicting evidence as uncertain.
Their public traces can be detected, but WordPress.org may not publish their releases. Latest version and vulnerability coverage can therefore be unavailable. Conflicting product identities are not automatically matched.
No. Matching compares observed versions with published data. Runtime configuration and exploitability are not tested. Follow the advisory and verify the installed version with the site administrator.
Initial connection failures produce an error. Later failures preserve available results and flag missing checks. An unavailable vulnerability source is never presented as a clean security result.