Transparent WordPress Security Assessments

WP Risk Scan Security Scan Methodology

Learn how WP Risk Scan evaluates publicly observable WordPress security signals, calculates security scores and turns findings into practical recommendations.

Our assessments use non-intrusive external requests. They do not require WordPress administrator credentials or install software on the target website.

How the Security Scan Works

  1. Validate the target. The scanner checks the submitted address and applies safeguards against requests to private or reserved network destinations.
  2. Assess availability and WordPress signals. Public responses are inspected to determine whether a WordPress assessment can proceed.
  3. Run security checks. The scanner reviews public-facing files, software indicators, authentication exposure, HTTP responses, TLS and DNS information.
  4. Evaluate findings. Findings contribute penalties to the security score according to the applicable check weights and critical-exposure rules.
  5. Generate a report. The report presents an overall score, grade, category results and prioritised remediation advice.

The 10 Assessment Phases

The current scanner processes ten phases. Some are preliminary checks or reporting stages rather than independent vulnerability tests.

1. Website Availability

Checks whether the target responds and whether an assessment can continue.

2. WordPress Detection

Looks for multiple publicly observable WordPress indicators, including on hardened sites.

3. Exposed and Sensitive Files

Checks for accessible backups, configuration files, debug logs, repositories and other sensitive resources, using content signatures to reduce false positives.

4. Core, Plugins and Themes

Reviews detectable software versions, WordPress.org information and known vulnerability data, including optional WPScan API coverage.

5. REST API and XML-RPC

Examines publicly observable API behaviour, user enumeration signals and XML-RPC functionality.

6. Authentication Exposure

Reviews login and registration exposure, author enumeration and visible authentication protections.

7. WordPress Hardening

Summarises selected externally visible configuration and hardening signals.

8. HTTPS and HTTP Headers

Reviews HTTPS enforcement, browser security headers, selected cookie flags and other observable response settings.

9. TLS and Email DNS

Checks certificate and protocol information together with public SPF, DMARC and CAA records.

10. Final Configuration Review

Completes the assessment and consolidates the results for reporting.

Check coverage can vary with website responses, access restrictions, network conditions and optional vulnerability-data configuration.

How the Security Score Is Calculated

WP Risk Scan starts with 100 points and subtracts penalties assigned by completed assessment phases. The resulting score is limited to the range of 0–100. Individual phase penalties are constrained by their configured weights.

When a critical exposure is identified – such as certain accessible configuration files, repositories, SQL dumps or an unfinished installer – the score is capped at 29 and the grade becomes F. The scoring engine also supports WordPress filters, so operators can customise scoring behaviour.

Default grade thresholds in WP Risk Scan 1.0.2
ScoreGradeInterpretation
95–100A+Excellent
90–94AExcellent
80–89BVery good
70–79CGood
55–69DFair
30–54ENeeds work
0–29FHigh risk

A score summarises the checks performed. It is not a certification of security and does not prove the absence of compromise or hidden vulnerabilities.

How Known Vulnerabilities Are Identified

The scanner attempts to identify publicly visible WordPress core, plugin and theme information and compare detectable components against available security information. Sources include built-in vulnerability data and, when configured, an optional WPScan API integration.

Version details may be hidden, inaccurate or unavailable. A component that cannot be identified cannot reliably be matched to a known vulnerability. The absence of a finding is not evidence that the component is secure.

Accuracy, Limitations and Responsible Interpretation

WP Risk Scan is an external risk assessment, not a penetration test, internal code audit or complete malware investigation. It cannot inspect private files, database contents, administrator accounts or every server-side configuration.

CDNs, firewalls, caching, redirects and rate limits may affect results. Some checks can be incomplete or produce findings that require manual verification. Always review the evidence and context before changing a production website.

Non-Intrusive Scanning and Responsible Use

WP Risk Scan uses read-only requests and a non-destructive XML-RPC method-discovery request. It does not attempt administrator logins, use credentials or exploit detected vulnerabilities. The service includes rate limiting and target validation safeguards.

Only scan websites you own or are authorised to assess. Website owners can request exclusion from scanning; the service supports an operator-managed domain opt-out list. Refer to the site’s Privacy Policy and Terms of Service for current operational and data-handling details.

Methodology FAQs

Does a score of 100 mean my website is completely secure?

No. It means the assessed checks did not result in deductions under the configured scoring rules. Hidden vulnerabilities and internal compromises may still exist.

Why can a critical exposure produce an F grade?

Specific high-impact findings trigger a critical-fail rule that caps the score at 29 and assigns an F grade.

Does WP Risk Scan exploit vulnerabilities?

No. It performs non-intrusive, read-only checks rather than exploitation or login attempts.

Can the scanner detect every installed plugin?

No. It can only identify components that leave sufficiently reliable publicly observable signals.

Why might results change between scans?

Software updates, server configuration, network conditions, access controls and vulnerability data can all change the observable results.