Skip to main content

phpcheck-url: Check PHP version from URL

Check the advertised PHP version and vulnerability status from a website URL or hostname using HTTP headers.

Source facts

Repository
openai/php2shell-checker
Last source activity
October 22, 2026 at 22:55
Detected SKILL.md language
English
Stars
836
Forks
83

Uses

Provide a website URL or hostname to check its PHP version.

Prerequisites

Requires Node.js.

How to use

  1. Navigate to the skill directory.
  2. Run the PHP check script with the target URL.

Limitations

Cannot verify backported security fixes in installed packages.

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
phpcheck-url
description
Check the advertised PHP version from a URL or hostname.
From this skill's directory, run: ```sh node scripts/phpcheck.js "https://example.com" --json ``` Use HTTPS for a bare hostname. The checker reads `Server` and `X-Powered-By` headers. If the version is hidden, report unknown. Versions below an upstream fix return `potentially_vulnerable` with exit code 1. PHP 5.4–5.6, 7.0–7.4, 8.0 and 8.1 also return this warning. A higher patch number on those branches, such as 8.1.35, does not establish a fix. Exit code 1 is a version-based warning, not proof that the installed package is unpatched. HTTP headers cannot tell whether the version contains a backported fix. Describe the result as potentially vulnerable, never confirmed vulnerable. An `ok` result with exit code 0 means only that the advertised stable version meets an upstream fixed release: 8.2.35, 8.3.36, 8.4.27 or 8.5.12. The installed build is not verified. Missing or unrecognized versions, prereleases and failed checks return `unknown` with exit code 3. Headers can be changed. A server-side check of the package serving the site is stronger evidence. Do not run exploit probes. Exit codes 1 and 3 are check results. Invalid arguments exit with code 2.
View on GitHub