phpwarden

Check a live site from the outside

phpwarden probe looks at a running PHP or WordPress site the way a visitor would and tells you what is exposed, ranked by what attackers are using. It reads; it never attacks.

Read the docsInstall the CLI

What it tells you

$ phpwarden probe https://client.example
phpwarden probe 2.4.0 -- https://client.example
mode: active  ownership: verified (well-known)  requests: 33
fingerprint: WordPress 6.4.2; 1 plugins; frameworks: wordpress

  HIGH     [EXPLOITED] WordPress core 6.4.2: unauthenticated local .php file inclusion ... CVE-2026-87902
  CRITICAL [EXPLOITED] plugin litespeed-cache 6.2: Unauthenticated privilege escalation ... CVE-2024-28000
  CRITICAL Exposed .env file -- 3 variables exposed (names only): APP_KEY, DB_PASSWORD, APP_DEBUG
  CRITICAL Exposed .git repository -- repository HEAD readable (ref: ...)
  MEDIUM   WordPress XML-RPC enabled -- XML-RPC enabled
  LOW      Missing Content-Security-Policy -- no CSP header
  ...
summary: 3 critical, 4 high, 4 medium, 4 low, 1 info; 3 known exploited

That is real output from a test site, shortened. Secrets are never copied into a report: an exposed .env is listed by variable name only.

For agencies and hosts

You look after sites you did not build and cannot always log in to. The probe needs nothing installed on the site: a URL and proof that you are allowed to check it. Run it when you take on a client, and on a schedule after that. It answers the question a client actually asks, "is anything on my site being attacked right now?", from the outside, in under a minute.

It works alongside the checks that run on the server. phpwarden wordpress and the WordPress plugin see every installed component; the probe sees only what the site shows a visitor. Use the probe where you have no server access, and both where you do.

The full check only runs on sites you can prove are yours

A tool that anyone can point at any site is a tool for attackers. So the active checks run only after you publish a token on the site, in one of three ways:

  1. a DNS TXT record: phpwarden-verify=<token>
  2. a file at /.well-known/phpwarden-verify.txt
  3. a <meta name="phpwarden-verify"> tag on the homepage

phpwarden probe https://client.example --print-token prints the token and the exact text to publish. On a site that has not been verified, the probe requests the homepage, looks for the ownership file, and stops.

What it never does

If you found this page in your server logs

A request with the User-Agent phpwarden-probe came from someone running the open-source phpwarden CLI against your site. If your site has not been verified by them, it received at most two requests: the homepage and /.well-known/phpwarden-verify.txt. To report misuse, write to [email protected].

Limits