Skip to main content

Guides

Website Vulnerability Assessment Explained

What a website vulnerability assessment involves, how it differs from penetration testing, and how to prioritise and fix the findings it produces.

Published
Updated
Reading time
6 min read
No threats foundMFA enforced

A website vulnerability assessment is a structured review that identifies known security weaknesses in your website, its software and the server it runs on. It answers a simple but important question: if an attacker looked at our site today, what obvious ways in would they find?

Most website compromises do not involve sophisticated, never-before-seen attacks. They exploit known issues: an outdated plugin with a published vulnerability, an exposed admin panel with weak credentials, a forgotten test copy of the site, or a server running software that stopped receiving security updates. A vulnerability assessment is designed to find exactly these problems before someone else does.

This guide explains what an assessment involves, how it differs from penetration testing, how findings are prioritised and what to do with the results.

Vulnerability assessment vs penetration testing

The two terms are often used interchangeably, but they describe different activities.

Vulnerability assessmentPenetration test
Main goalIdentify and prioritise known weaknesses across the estateDemonstrate how far an attacker could get by actively exploiting weaknesses
ApproachAutomated scanning combined with manual review and verificationPrimarily manual, creative testing by specialists
Breadth vs depthBroad coverageDeep focus on agreed targets
FrequencyRegularly, and after significant changesPeriodically, or before major launches
Typical outputPrioritised list of findings with remediation adviceNarrative of attack paths and impact, plus findings
Risk to the live siteLow when scans are configured carefullyRequires careful scoping and agreed rules of engagement

For most small and mid-sized businesses, a regular vulnerability assessment combined with good patching delivers the most risk reduction for the effort. Penetration testing becomes valuable for custom applications, high-value targets, or where contracts and frameworks call for it.

What a website vulnerability assessment typically checks

Software versions and known vulnerabilities

The assessment identifies the CMS core, plugins, themes, extensions, libraries and server software in use, and compares their versions against public vulnerability databases. For WordPress, WooCommerce and Magento sites, outdated extensions are consistently among the most common findings. See what happens when you don't update WordPress for why this matters.

Server and hosting configuration

  • Operating system and runtime versions, including whether they are still supported. PHP versions, for example, have published end-of-life dates after which they stop receiving security fixes.
  • Open ports and exposed services, such as databases or admin interfaces reachable from the internet.
  • Directory listing, default pages and verbose error messages that leak information.
  • File and folder permissions that allow more access than necessary.

TLS and HTTP security headers

Checks cover certificate validity, supported TLS versions and cipher suites, HTTP to HTTPS redirection, and security headers such as Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options and Referrer-Policy.

Authentication and access

  • Login pages exposed without rate limiting or multi-factor authentication.
  • Default or predictable usernames.
  • Unused administrator accounts.
  • Exposed admin paths and management tools such as database administration panels.

Common web application weaknesses

Scanners and manual checks look for classes of issue described in the OWASP Top 10, such as injection, broken access control, cross-site scripting and security misconfiguration. Automated tools can highlight candidates, but findings need human verification to separate real issues from false positives.

Exposed files and forgotten assets

Backup archives in the web root, exposed version control folders, old staging sites, configuration files and log files are surprisingly common and can leak credentials or source code.

Preparing for an assessment

A little preparation makes the assessment safer and the results more useful.

Agree the scope

List the domains, subdomains, servers and applications to be assessed. Include staging sites, APIs and admin interfaces, because these are often less well protected than the main site. Confirm that you own or are authorised to test everything in scope, especially where third-party hosting or SaaS platforms are involved, since some providers have their own testing policies.

Decide between unauthenticated and authenticated testing

An unauthenticated assessment sees what an anonymous attacker would see. An authenticated assessment, using a dedicated test account, can also review areas behind the login, such as customer accounts or administrator functions. Many businesses benefit from both perspectives.

Take a backup and choose a time

Even careful scanning sends unusual traffic. Take a verified backup beforehand, schedule scans outside peak trading periods, and let your hosting provider know if their own security systems might block or flag the activity.

Gather what you already know

Share a list of installed plugins and integrations, recent changes and any known issues. This helps the assessor focus manual effort where it matters and reduces false positives. It is also worth naming who will receive the report and who has authority to approve fixes, so that critical findings can be acted on the same day rather than waiting for the next meeting.

How findings are prioritised

A raw scan can produce hundreds of results. The value of an assessment lies in turning that list into a short, prioritised plan.

Severity is often expressed using the Common Vulnerability Scoring System (CVSS), which rates vulnerabilities from 0 to 10. CVSS is a useful starting point, but context matters just as much:

  • Exploitability: is there a public exploit, and is it being actively used?
  • Exposure: is the vulnerable component reachable from the internet, or only behind authentication?
  • Impact: would exploitation expose customer data, payment flows or administrator access?
  • Compensating controls: does a web application firewall or configuration already mitigate the issue?

A typical prioritisation might look like this:

  1. Critical: actively exploited vulnerabilities in internet-facing components; fix immediately.
  2. High: serious weaknesses with a realistic attack path; fix within days.
  3. Medium: issues that increase risk or would help an attacker; schedule into maintenance.
  4. Low and informational: hardening improvements and best-practice recommendations.

Acting on the results

An assessment that produces a report and nothing else has limited value. The real risk reduction comes from remediation.

Patch and update

Most findings are resolved by updating software. Apply updates safely, using a pre-update backup and staging where possible, so that fixing a vulnerability does not break the site. A structured security patch management process makes this routine rather than reactive.

Remove what you do not need

Deactivated plugins, unused themes, old admin accounts, abandoned staging sites and leftover backup files all add risk with no benefit. Removing them is often the quickest win.

Harden configuration

Restrict admin access, enforce multi-factor authentication, tighten file permissions, disable directory listing, add security headers and close unnecessary ports. Our WordPress security hardening checklist covers these steps for WordPress sites.

Add protective layers

A properly configured web application firewall can block many common attack patterns and provide virtual patching while fixes are tested. It is a valuable layer, but not a substitute for updating the underlying software.

Verify the fixes

Rescan after remediation to confirm issues are resolved, and record what was changed. This creates an audit trail that is useful for internal governance and for frameworks you may need to evidence.

How often should you assess?

A sensible baseline for most business websites is a regular scheduled assessment plus additional checks after significant changes, such as a redesign, platform upgrade, new integration or hosting migration. Continuous automated scanning for known vulnerabilities in installed components, combined with periodic deeper reviews, works well for most organisations.

If you process card payments, PCI DSS requires quarterly external vulnerability scans by an Approved Scanning Vendor for many merchants. If you handle personal or health data, frameworks such as GDPR or HIPAA expect appropriate technical security measures. SupportSafe supports the technical controls and evidence, but does not provide legal or compliance certification advice; confirm your specific obligations with your compliance adviser or acquiring bank.

Where SupportSafe fits

Our vulnerability assessment service combines automated scanning with manual verification, so you receive a prioritised, plain-language report rather than a raw scanner export. Because we also carry out ongoing website security and maintenance work, findings can be remediated, verified and tracked through monthly reports rather than left in a PDF.

Next steps

If your website has not been assessed in the past year, or has changed significantly since it was, an assessment is a practical way to understand your current exposure. Start with our free website health check for an initial view, or get a quote for a full vulnerability assessment of your website and server.

Frequently asked questions

Will a vulnerability scan slow down or break my website?
A carefully configured assessment is designed to have minimal impact. Scans can be throttled, scheduled for quieter periods and excluded from sensitive actions such as placing orders. Discuss scope and timing before any scan runs.
Is an automated online scanner enough?
Automated scanners are useful for spotting known issues, but they produce false positives and miss context. Manual verification and prioritisation turn raw results into a practical remediation plan.
Do I need a penetration test as well?
Many small and mid-sized business websites get most value from regular vulnerability assessments and good patching. Penetration testing is worth considering for custom applications, sensitive data or where contracts and frameworks require it.
What happens after the assessment?
You should receive a prioritised list of findings with remediation guidance. The most important step is fixing critical and high findings promptly and rescanning to confirm they are resolved.

SupportSafe Engineering Team

Maintenance, infrastructure and security engineers

Articles are written and technically reviewed by the SupportSafe engineers who carry out website, application and server maintenance for our clients. Each article is reviewed for accuracy before publication and updated when practices change.

Let's take responsibility for your technology.

Tell us what you run and what keeps you up at night. We'll assess it and recommend a maintenance plan that fits – with no obligation.