Website Checker / Known vulnerabilities
Website vulnerability check: known CVEs in your site's software
Whether the versions we could see appear in public vulnerability databases (OSV, which includes CVE entries) or in the WordPress.org list of insecure versions.
What the colours mean
- OK. No known vulnerabilities in the versions we could see.
- Needs attention. Known vulnerabilities of low or moderate severity were found.
- Problem. Known high-severity vulnerabilities were found, or the platform version is marked insecure.
Why it matters for your business
- A published vulnerability comes with instructions — attackers do not need to be skilled to use it.
- Typical results: injected spam links, redirects to scam sites, stolen form data.
- We only see what the site shows publicly; the real number can be higher.
What you can do yourself
- Update every component named in the report to its latest version.
- Remove plugins and scripts you no longer use.
- Set up regular automatic updates or a maintenance plan.
What OLBO can do
Technical website audit — from €490, 2 working days: a report with exact instructions for your developer.
When the platform itself is old, patching costs more every year. A new site on a current platform fixes this indicator together with speed, security and accessibility.
Common doubts
Does a known vulnerability mean we have been hacked?
No — it means the door is publicly known. Closing it now is much cheaper than cleaning up later.
Why can't you list every vulnerability?
We only see versions the site shows publicly. A manual technical audit looks deeper.
What this usually costs
Approximate prices from open sources — for orientation only.
| USA | $800–2,400 |
|---|---|
| Europe | $400–1,600 (UK) |
| OLBO | from €490 |
Estimate: a technical audit takes about 8–16 hours × average agency hourly rates (Clutch). Sources: Clutch «Web design pricing» (updated 21 September 2026). Prices vary with scope; OLBO prices are fixed after a free brief.