webskan
BlogPricingFAQPL

Security score: what we check and how it is calculated

The “Security” score (0–100) shows how many weak points of a site are visible from the outside – the way anyone visiting the site sees them, including bots looking for easy targets. We break nothing and log in nowhere.

Example: what a result looks like

A real audit result for a company website running WordPress, from 21 November 2026 (address withheld). Of its 13 security findings we show three – one of each severity.

Security

25 out of 100. Where the score comes from: 1 important finding (−25), 4 “worth fixing” (−32), 3 minor (−6) and 5 missing headers (−12, the cap). 100 − 25 − 32 − 6 − 12 = 25.

  • importantWordPress 5.5.24 – a version WordPress.org marks as insecure

    The page source states WordPress 5.5.24. The WordPress.org version catalogue marks it “insecure”: later releases fix known vulnerabilities (latest version: 7.1.5). Update WordPress – at least to the last maintenance release of your branch – and enable automatic minor updates.

  • worth fixingPlugin “Slider Revolution” 5.4.7.2 – 14 entries in public vulnerability databases

    Version 5.4.7.2 was read from the “generator” tag in the page source. Public vulnerability databases (CVE records) cover this version in 14 entries; the highest-scored: CVE-2023-6528, score 8.8/10 – remote code execution. Version ranges come from the issuers of the entries; whether a given entry applies to this site depends on its configuration (enabled features, form fields, user roles, other plugins; an older version may not have the feature yet) and cannot be confirmed from outside. Update to the latest version; if the author has not released a fix, consider disabling or replacing the component. If your admin panel already shows a newer version, ignore this finding.

  • minorWordPress XML-RPC interface is enabled

    /xmlrpc.php responds. It is used for bulk password guessing and amplification attacks; unless you use the WordPress mobile app or Jetpack, disable it.

Note the second item: the highest-scored entry is 8.8/10, yet the finding is of medium severity. From outside we can see the plugin version, but not whether a given entry applies to this particular site – so only a vulnerability known to be exploited in real attacks (the CISA KEV list) is rated “important”. The advice is the same in both cases: update.

What we check

  • Known vulnerabilities in the site’s software. We read what the site is built with (WordPress, plugins, theme, libraries) and in which versions, then compare that with a database of published vulnerabilities. The result: “plugin X version Y has a known vulnerability, the fix is in version Z”.
  • Unsupported versions. A WordPress release that WordPress.org marks insecure, PHP past end of life, plugins removed from the directory.
  • Files that should not be visible. Backups, database dumps, configuration files, a code repository, error logs, a database panel.
  • The connection. The certificate and its expiry, the redirect to HTTPS, resources loaded without encryption.
  • Mail spoofing protection. The domain’s SPF and DMARC records – they decide whether someone can send e-mail “from you”.
  • Server and WordPress settings. Security headers, session cookies, a public account list, XML-RPC, directory listing.
  • Django applications. An admin panel open at the default /admin/ address and DEBUG mode left on in production (the error page then exposes the application’s internals).

How the score is calculated

We start from 100 points and subtract for every finding:

Finding weightPointsExample
important−25a WordPress version that WordPress.org marks as insecure; a component with a vulnerability on the CISA KEV list (exploited in real attacks); a publicly reachable database backup; an application left in DEBUG mode
worth fixing−8no DMARC record; a plugin or theme in a version covered by entries in public vulnerability databases (entry scored 4/10 or higher, or unscored)
minor−2XML-RPC enabled; an outdated plugin with no known vulnerabilities
  • Missing security headers subtract at most 12 points in total – headers alone do not turn a site red.
  • One “important” finding caps the score at 49. A site with a serious vulnerability does not get an amber score because everything else is fine.
  • Colours: 90–100 green, 50–89 amber, 0–49 red.

The same formula runs in the free scan, the in-depth audit and Monitor, so results can be compared over time.

A new vulnerability? Monitor tells you

Vulnerabilities are published every day, including for versions that were safe yesterday. Webskan Monitor compares the site’s software with the database once a day and e-mails you when a new entry appears: which component, what kind of vulnerability, how it was scored, and which version to update to. Each vulnerability is reported once.

How we know about vulnerabilities

We maintain our own database of known vulnerabilities in website software – about 40,000 entries today for over 12,000 WordPress plugins and themes and popular libraries – refreshed several times a day from public, official sources (listed below). Every finding carries a CVE number, so it can be checked at the source.

A plugin’s version is read from files the site itself serves. If the site does not reveal a version we say “nothing to compare” – we do not guess.

What the score does not tell you

  • 100 does not mean “cannot be hacked”. We cannot see the admin panel, passwords, server-side code or plugins that leave no trace in the page source.
  • A known vulnerability does not mean “the site is hacked”. It means this version has a documented flaw and is worth updating before someone uses it.
  • The admin panel is authoritative. If Plugins → Installed shows a newer version than our reading, the finding can be ignored.
  • We do not run penetration tests: no login attempts, no form submissions, no checking whether a vulnerability is exploitable. Scanner traffic details: webskan.com/bot.

Data sources and licences

  • CVE Program (cve.org) – CVE records with version ranges, published among others by Wordfence, Patchstack and WPScan as CVE Numbering Authorities. Copyright © The MITRE Corporation. “MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE™). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.”
  • CISA Known Exploited Vulnerabilities – vulnerabilities exploited in real attacks (CC0 1.0).
  • WordPress.org – WordPress version status, latest plugin versions, plugin closure information.
  • retire.js – known vulnerabilities in JavaScript libraries (Apache License 2.0).
  • WPVulnerability (wpvulnerability.net) – supplementary version ranges for plugins and themes (CC0 1.0 data).
  • endoflife.date – software end-of-life dates (MIT License).

Webskan is not affiliated with or certified by any of these organisations. The plain-language descriptions of vulnerabilities are ours.

Building your own Python or Node.js application? The versions of its libraries are not visible from outside – check them separately: project dependencies.

Check your site

© 2026 Webskan · Blog · Terms · Privacy policy · For developers · contact: kontakt@webskan.com