Sample £149 Check Report

Exactly what you get for £149: the confirmed version, the exposure verdict, the configuration details that matter, and the recommended next step in writing.

Worked example — hypothetical site, real advisory facts.

PHP CHECK REPORTHypothetical store · reference EX-0001

1. What we were given

  • Site type: WooCommerce store (WordPress 6.9.1, 14 active plugins)
  • Stated PHP version: unknown — the customer left the field blank
  • Hosting: shared hosting, cPanel panel, PHP-FPM
  • Access: none yet — findings are from the customer-supplied phpinfo output and Site Health export

2. Version and exposure

  • Confirmed PHP version: 8.2.31 (web SAPI), 8.2.31 (CLI)
  • Fixed release for this branch: 8.2.35 (21 Oct 2026)
  • Verdict: EXPOSED — patch level 31, fix released at 35. CVE-2026-109618 and CVE-2026-109619 affect this site until PHP reaches 8.2.35 or later.
  • WordPress core 6.9.1: not itself the issue; no core action needed from us

3. Configuration notes

  • display_errors: On — recommended Off in production (leaks paths and details to attackers)
  • OPcache: enabled — patch will require a PHP-FPM restart to take effect (noted for the patch job)
  • PHP version control: via cPanel MultiPHP — emergency patch is a supported job
  • No staging environment detected — the £249 add-on applies if the patch is booked

4. Recommended actions, in order

  • 1. Book the £999 emergency patch; we move PHP to 8.2.35 with a backup, staging test and smoke test. Recommended within days, not weeks — this is an actively relevant CVE pair.
  • 2. Add the £149 plugin & theme compatibility pass: 14 active plugins means real surface area for the patch to upset.
  • 3. Add the £249 staging setup, since no staging environment exists and patching without one means touching production blind.
  • 4. Plan a version upgrade to a supported branch: PHP 8.2 reaches end of life 31 Dec 2026, which leaves roughly ten weeks after the patch lands.

5. What this report does not cover

  • Compromise assessment: a patch closes the hole; it doesn't determine whether someone came through it first. Ask separately if you suspect an incident.
  • No plugin-level code review was performed (that's part of the paid upgrade), only the patch-exposure picture.
  • The £149 check fee is not credited against the patch or upgrade.
End of report — real reports are emailed as a PDF on the letterhead of the booking.

The report above is a worked example using a hypothetical store — no real customer data anywhere in it. It shows the structure and depth every £149 check report delivers.

Real customer reports carry their own site details; those details never appear here.

Reports are produced and reviewed by a person, not an automated scanner — the verdicts and recommendations are argued, not aggregated.

Get Yours for £149

Secure your place in the queue and the report lands in your inbox — typically within two working days of the checks running.

Book the £149 checkService terms