WordPress site checks

WordPress vulnerability scan from the outside

The versions your site shows to anyone, matched against published vulnerabilities, plus the files, accounts and settings an attacker looks for first.

  • AccessNone
  • RunsWeekly, key pages daily
  • OutputReport with ranked fixes
  • PriceFree to start

The checks

What an attacker sees first

  1. Versions with known flaws

    WordPress, plugin and theme versions visible from outside, matched against WPVulnerability's public data.

  2. Files that should not be public

    readme files that show the version, backups, debug logs and installers left on the server.

  3. Accounts and login

    Usernames listed by the REST API or author pages, and whether XML-RPC accepts logins.

  4. Headers and certificate

    The six security headers browsers honour, the certificate's expiry and the domain's renewal date.

  5. Email spoofing

    Whether SPF and DMARC stop someone sending mail as your domain.

Example

What the security reads found

The same reads on your site, with the fix for each.

wpcomm.itRead 4 November 2026, outside checks
  • FailSecurityNone of six security headers is setFix: add them at the server or in a small plugin
  • WarnSecurityreadme.html is public and the REST API lists one usernameFix: block both; neither is needed by visitors
  • WarnEmailDMARC only reports on forged mail and lets it throughFix: move the policy from none to quarantine
  • OKCoreWordPress 7.1.4, the current release
  • OKCertificateValid until 30 December 2026 and renews itself

wpcomm.it, read from outside on 4 November 2026 before this rebuild. The same checks run on your site.

Scope

What the check covers and what it does not

Included

  • Core, plugin and theme versions visible from outside
  • Public files, user listing and XML-RPC
  • Security headers, certificate and domain expiry
  • SPF and DMARC
  • Changes since the last run

Not included

  • Penetration testing
  • Malware removal, which we quote at a fixed price
  • Plugins the site does not show to visitors, which the read-only plugin adds from the Site plan
Access
None
First report
One business day
Data
WPVulnerability, CC0
Price
Free to start

How it works

From a site address to a report in one business day

The checks run without anyone on your side, and a person joins only when you ask for one.

  1. 1

    Send the address

    No access and nothing to install. We read the site from outside, the way a visitor and Google see it.

    Takes two minutes

  2. 2

    Read the first report

    Every finding with what we read and what fixes it, worst first.

    Within one business day

  3. 3

    Start free

    500 credits cover the first runs, and 3 pages are checked every day after that. After the first report you hear only about what changed.

    No card needed

  4. 4

    Pick a plan when you want more

    More checks and tests, run more often, on more sites. When you want engineers on the fixes, a managed plan adds them.

    From $19 a month

  • 11WordPress core contributors on the engineering team that reviews findings
  • 565+custom plugins shipped by the same team
  • 1business day to your first report
  • $19a month for the first paid plan, after a free start

The checks read public vulnerability data from WPVulnerability and Google's field and lab data from PageSpeed Insights.

From a client of the team

"…they manage to turn around the trickiest tasks in record time."

Head of FranchiseA multi-location entertainment franchise, in a Clutch review of the team

Fit

Who the checks are built for

A good fit if

  • Your company sells, books or takes leads through a WordPress site
  • Revenue between about $20M and $100M, or a site that carries a business that size
  • A developer or agency already works on the site and you want an independent view
  • Someone senior wants a weekly answer without hiring for it

Not a fit if

  • Agencies reselling checks to their own clients
  • A personal blog or a one-page brochure site
  • A site that is down today and needs incident help
  • A site that is not WordPress

Questions

Questions buyers ask first

Anything else goes in the form, and we answer in writing.

Is this a penetration test?

No. It reads what the site shows to anyone and reports what is exposed. It sends no attack traffic.

Can you see every plugin?

Only the ones the site reveals from outside. From the Site plan, the read-only plugin lists every plugin and version.

What if you find a hacked site?

We tell you the same day, with what we saw. Clean-up is quoted at a fixed price.

Start

See what an attacker sees every week

If the site is not a fit we say so in the same reply, and nothing is charged.

Stored and read by a person. Deleted after 12 months.

  1. 1

    TodayWe check that the site is WordPress and that the plan fits it.

  2. 2

    Within one business dayYour first report, with the tests that can start on your site and the plan they fit.

  3. 3

    After thatReports on your schedule, and an email the day a check fails.