ModelGain PHP Security Monitor provides conservative PHP vulnerability evidence, optional scheduled checks, and actionable hosting-side remediation guidance. It does not modify PHP or promise continuous protection.
Tools > PHP Security shows the PHP_VERSION and PHP_SAPI serving the actual admin request. It never executes shell commands, displays phpinfo, probes exploits or changes PHP configuration.
After explicit opt-in, Check now retrieves WPVulnerability's PHP branch advisories and lifecycle. The plugin locally applies both minimum and maximum version predicates; the API returns the entire branch history, not only advisories affecting your exact version.
A matching upstream version is labelled potentially affected, never confirmed exploitable. Operating system, SAPI, extensions, application usage, configuration and vendor backports may change applicability. Advisory severity is not a measure of verified server exposure. No matches are not a guarantee of security. App-level code cannot independently verify distributor backports.
Lifecycle is provider-reported, separate from vulnerability severity and applicability. There is no bundled offline lifecycle table: without usable evidence it is unknown. Consult
https://www.php.net/supported-versions.php and your hosting provider for independent support/build information.
The copyable host-support report includes evidence, timestamps and questions about package/backport status and conditional applicability. It is never sent by the plugin. Remediation belongs with the hosting provider; updating WordPress cannot patch the PHP interpreter. Test compatibility in staging before changing PHP, then recheck the web runtime.
Optional monitoring requires separate explicit scheduled-query AND email consent after manual consent. WP-Cron checks approximately every six hours; traffic, disabled cron or failures may delay checks indefinitely. CLI/phpdbg cron is skipped because it cannot establish the web runtime. The first complete fresh scan establishes a baseline and sends one initial alert when potential vulnerability matches or upstream EOL exist; an initial scan without these findings is silent. Later fresh state changes send event summaries for new potential matches, records no longer matched/listed (not proof of a fix), and upstream EOL. Unknown/partial evidence never proves resolution. After 48 hours without fresh evidence, one failure alert is attempted per incident, rearmed only by fresh evidence. A cron outage cannot notify about itself.
Emails use core wp_mail and go only to the site administration address. True means accepted by the transport, NOT delivered. Check inbox/spam and configure WordPress mail independently. Automatic attempts are claimed before sending: failed or interrupted sends are not retried, preventing spam but potentially losing an alert. Use the administrator Test email button (once per minute). Tools > PHP Security shows last run, freshness, next scheduled check and last mail status. Disable monitoring cancels its schedule and email state while retaining manual consent; deactivation disables it too.
There is no automatic update/fix mechanism, telemetry, account, SaaS dependency, paid feature or custom database table. Normal WordPress core update behavior is unchanged.