server
Skill2 starsChanged 25 days agoApache-2.0View on GitHub
Check whether the PHP serving a site on this machine or server is patched against PHP2Shell (October 2026 PHP security releases). Use when the user has local or SSH access and asks if their PHP install is vulnerable or patched.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- DegreeSign/skillstheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- DegreeSign/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- urlSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Check the PHP version serving the site.
- Very specific: line 51
If the user cannot update immediately, the advisory lists measures that reduce exposure but do not make an installation safe, such as …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PHP2Shell refers to CVE-2026-109618 (RCE via OOM corruption) and CVE-2026-109619 (RCE via stale global state), fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21, 2026 (https://www.php.net/archive/2026.php#2026-10-21-5). They affect every PHP installation serving web requests: PHP-FPM, Apache with mod_php (highest risk), php-cgi, FrankenPHP and LiteSpeed.
Check the PHP version serving the site. Start with php -v, but verify that
it matches the site's PHP-FPM or Apache installation. The CLI binary is often
a different version from the one that serves web requests. Look for
php-fpm* binaries, the web server's PHP handler, or a phpinfo() page the
user already has.
Vulnerable ranges used by the checker as of October 20, 2026:
| PHP branch | Vulnerable range (inclusive) |
| 5.4 | 5.4.0 to 5.4.45 |
| 5.5 | 5.5.0 to 5.5.38 |
| 5.6 | 5.6.0 to 5.6.40 |
| 7.0 | 7.0.0 to 7.0.33 |
| 7.1 | 7.1.0 to 7.1.33 |
| 7.2 | 7.2.0 to 7.2.34 |
| 7.3 | 7.3.0 to 7.3.33 |
| 7.4 | 7.4.0 to 7.4.33 |
| 8.0 | 8.0.0 to 8.0.30 |
| 8.1 | 8.1.0 to 8.1.34 |
| 8.2 | 8.2.0 to 8.2.34 |
| 8.3 | 8.3.0 to 8.3.35 |
| 8.4 | 8.4.0 to 8.4.26 |
| 8.5 | 8.5.0 to 8.5.11 |
Compare the version and full package revision with current PHP or vendor
security advisories. Vendor backports may fix an older version. For a
distribution package, check the installed package revision (for example with
dpkg -l 'php*' or rpm -qa 'php*') against the vendor's advisory. Treat
unlisted branches as unknown until an advisory confirms their status.
PHP 8.1 and older received no upstream release. They are fixed only by a
distribution or LTS vendor backport, or by a build from the PHP security
team's source backport branches for 7.4, 8.0 and 8.1. These builds keep the
old version number, so confirm the build source before reporting them as
patched. Packages from rpms.remirepo.net were not updated on release day.
If the user cannot update immediately, the advisory lists measures that reduce
exposure but do not make an installation safe, such as
session.upload_progress.enabled=0 and a low post_max_size set in
php.ini or the FPM pool, followed by a restart of every worker. Point the
user to the advisory for the full list, and always say that updating is the
only complete fix.
The running PHP build and the vendor's package advisory are the useful checks. Configuration settings alone do not establish that PHP is patched. Report the version, patch status, and any required update. If you cannot verify the serving version, report unknown. Do not run exploit probes.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.