Administrators use PHP CLI to run maintenance scripts, scheduled jobs, dependency tools and framework commands. The executable is commonly named php, although a server with several PHP versions may have multiple binaries with different names or paths.
CLI and web-serving PHP can use different executables, configuration files and extensions. Typing php -v into a terminal reveals the CLI version selected by that shell. It does not by itself identify the PHP-FPM pool, Apache module or hosting-panel handler that serves a website.
This difference causes false confidence during security checks. A freshly updated CLI binary can coexist with an old web-facing runtime, and a web runtime may be patched even when the default CLI command points elsewhere.
Check both environments when a security advisory affects PHP. Record the executable path and version for scheduled jobs, then separately inspect the handler that processes HTTP requests for each affected site.