We only look at what any visitor sees: no brute force and no login attempts.
The result will appear here: the WordPress version, theme and plugins, which have known vulnerabilities and what version to update to.
This site does not look like WordPress: we found neither its paths nor its signature. If it is, it may hide it well; try the SEO audit or the security headers checker.
Plugins that load nothing on the home page cannot be seen from outside: the report covers the ones that can.
Shall we secure it for you?
We update with backups, close what is exposed and email you the full PDF report.
Full report
Take the report as a PDF
The detail of each vulnerability is not shown on the page: it goes in the PDF, just for you. If you like, we also tell you how we would secure it.
- The list of vulnerabilities for each plugin, theme and the core, with its CVE and severity
- What version to update each component to in order to close them
- What is left exposed (users, XML-RPC, files) and how to close it
- A plan of what to fix first
How to use it
01
Type your domain
One of your WordPress sites or a client’s.
02
We look from outside
We detect core, theme and plugins with their versions and cross-check them with vulnerability databases.
03
Read the result
What to update and to what version. Leave your email and we send the detail of each vulnerability as a PDF.
What does it check?
- Core
- WordPress version against the latest release and its known vulnerabilities.
- Plugins and theme
- Those visible from outside, with their version: vulnerable, outdated or removed from WordPress.org.
- Exposure
- Usernames published in the API, XML-RPC, accessible debug log, uploads folder listing and readme.html.
Vulnerability data: WPVulnerability (CC0) and Wordfence Intelligence. Versions: WordPress.org.
Frequently asked questions
Is it legal to scan a WordPress site?
This scanner only looks at what any visitor sees when opening the site: the page code, the plugins’ public files and a few well-known addresses. It does not try passwords, does not attempt to log in and does not make hundreds of requests. It is the same information a search engine would read.
Why does it not detect all my plugins?
A plugin that loads nothing on public pages leaves no trace from outside, and we do not search for them blindly: that would mean thousands of requests against the site. If you want the full list, we review it with dashboard access.
Where do the vulnerabilities come from?
From WPVulnerability, an open database that gathers CVE, Wordfence, Patchstack and WPScan, and from Wordfence Intelligence. The latest version of each plugin and whether it was removed come from WordPress.org.
Why is the detail in the PDF?
A public list of a site’s flaws is a guide to attacking it. The page shows what to update and how urgently; the list of each vulnerability with its CVE is sent only to whoever leaves their email.
Is the result stored?
It is kept for 24 hours on our server so we can email you the report, and then deleted.
Background reading
Explained on the blog
Critical PHP and Node.js vulnerabilities: what happened and what to do
On October 21, PHP and Node.js shipped fixes for serious flaws that allow code to run on the server. What they mean in plain language, which versions fix them and what to do this week.
What to do if Google flags your site as dangerous
Why Chrome's red screen appears over a website, what is usually behind it, how to clean the site properly and how to ask Google to lift the warning.
How to find out what a website is built with
The clues any site leaves about its CMS, its framework and its hosting, how far you can trust them, and why it helps to know before a redesign or a migration.
Security
Keep checking
Headers that protect your visitors, Google’s blocklists, and passwords that are already out there.
- Security headers checkerHSTS, CSP, X-Frame-Options and friends: which ones you have, which are missing and what each protects.
- Safe Browsing checkerQuery Google’s Safe Browsing list: malware, phishing and unwanted software.
- Pwned password checkerCheck whether a password appears in known breaches without it ever leaving your browser.
Rather have us check it for you?Continuous support & evolution
Next step
Does your WordPress need a hand?
Updates with backups, cleanup if someone already got in, and monthly maintenance so it does not happen again.
or reach us onWhatsAppinfo@einscube.com
What happens next
- You tell us about the projectA short form, no strings attached.
- We reply within one business dayWith a first read on scope.
- Scoping call and proposalWe set it up by email and send you the proposal.
We reply within one business dayBogotá · UTC−5