The Version Exposure tab helps identify selected PHP support-lifecycle and billing-platform update concerns. Use its findings to plan a compatible update, rather than treating it as a complete vulnerability scan.

Read the report

1. Open PD Modules → Guard → Version Exposure with Pro access active.
2. Check the displayed WHMCS and PHP versions. The PHP version is the runtime serving this page; a scheduled task can use a different runtime.
3. Read each finding’s severity, version and detail, including any advisory link.
4. Read the explanatory note below the findings, especially whether checking for a newer WHMCS release was possible.

The report evaluates known version values against its included rules. It does not query a live catalogue of individual vulnerabilities, test whether a particular exploit works, or prove that all installed extensions are up to date.

Understand a clean result

Nothing out of date means no finding was produced by those checks. It does not prove that the installation has every available security fix. A missing latest-release value prevents that update comparison; an unknown PHP branch is not automatically classified by a rule for another branch.

For WHMCS, the update comparison uses the latest-release value already recorded by WHMCS. A missing or stale update-check value limits the result. The report’s broad version floor is also not a statement that every release above it remains supported.

Check current support and compatibility

Use PHP’s supported-versions table for current branch support. The module’s included support dates cannot cover every future branch or later policy change. Check WHMCS’s requirements and your installed modules before selecting a replacement PHP version; support by PHP alone does not establish application compatibility.

Review the platform’s own release notes and security information, take the backups required by your normal maintenance process and plan the update with your hosting administrator. This tab does not perform that update. After maintenance, reload it and confirm that the displayed versions reflect the intended change.

Do not run internal repair commands or choose a new PHP branch solely to remove the headline warning.

See the PD Guard WHMCS guide for related tasks, or explore PD Guard.