Over the last few days, there's been an huge Internet
upheaval over PHP.
Two different researchers, both using (ObSF) AI tools to
analyze source code, found a vulnerability in all
versions of PHP which permitted foreign code
execution without authentication. Essentially,
this would give any outsider with access to the
server more or less complete access to the
systems.
Patches have been sent out, but a huge number
of sysadmins (70% of internet websites use PHP)
spent a *very* long Wednesday patching systems.
Many, many systems were shutdown until the fixes
could be applied.
This is a near-SF type discovery, and its highly
probable that many other vulnerabilities exist in
widely used software, just waiting for the proper
AI query to show themselves. Perhaps to hackers,
perhaps to AIs that are feeling hackerish themselves.
CISA announcement recommending shutdowns. https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching--
Wikipedia history: https://en.wikipedia.org/wiki/PHP2Shell
pt
On 2026-10-23, Cryptoengineer wrote:
Over the last few days, there's been an huge Internet
upheaval over PHP.
Two different researchers, both using (ObSF) AI tools to
analyze source code, found a vulnerability in all
versions of PHP which permitted foreign code
execution without authentication. Essentially,
this would give any outsider with access to the
server more or less complete access to the
systems.
Patches have been sent out, but a huge number
of sysadmins (70% of internet websites use PHP)
spent a *very* long Wednesday patching systems.
What was the reason why this was disclosed directly to public knowledge instead of following the usual route of allowing for a fix to be
developed first?
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 59:33:34 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
4 files (9,632K bytes) |
| Messages: | 286,017 |