Attack Attempts Hit PHP2Shell Flaws Before Patch Landed

Attackers exploited two critical PHP flaws before their October 21 patch, and CISA has added them to its known-exploited vulnerabilities catalog.

@sharedot

Attack Attempts Hit PHP2Shell Flaws Before Patch Landed

By @sharedot · · 6 pages

  • Programming
  • Security
  • Php
  • Php2shell
  • Cisa

Attackers exploited two critical PHP flaws before their October 21 patch, and CISA has added them to its known-exploited vulnerabilities catalog.

Two critical PHP flaws power the exploit chain called PHP2Shell

Security teams are racing to patch two critical vulnerabilities in PHP, the programming language that, per the CBS News Fact Check Team, powers roughly 70% of the world's websites.

The flaws, collectively dubbed PHP2Shell, allow an unauthenticated attacker to execute code remotely on an affected server without logging in. Both received a severity score of 9.2 out of 10 under the CVSS version 4.0 scoring system, indicating a critical security risk.

PHP developers released security updates on October 21, urging administrators to update affected systems immediately, and the official PHP security advisory lists the fixes and affected versions.

Because PHP underpins content management systems and platforms that handle sensitive customer information, the exposure surface is enormous — and the window between patch release and full deployment is where the danger lives.

The surprising part: attackers moved before the patch did

The development that has working programmers talking is the timeline.

According to CBS News, security researchers reported exploitation attempts that included activity before the security updates became available, and BleepingComputer reported that researchers documented attempts targeting the flaws before public disclosure.

JD Supra's analysis carries the same warning in its headline: attack attempts preceded the PHP2Shell patch, a fact it frames as a lesson for third-party risk programs. That reversal of the usual patch-then-exploit sequence matters because AI played a role on both sides.

Per CBS News, researchers used artificial intelligence to help identify and demonstrate the weaknesses — but the same discoveries can help malicious actors understand how to target systems that have not been updated.

The evidence: CISA listing and honeypot hits

The exploitation evidence stacks up quickly. On October 26, the U.S. Cybersecurity and Infrastructure Security Agency added both vulnerabilities to its Known Exploited Vulnerabilities Catalog, which identifies flaws with evidence of exploitation and helps organizations prioritize fixes.

On October 27, cybersecurity reporting described evidence of successful exploitation against honeypot systems — deliberately exposed systems researchers use to detect and study attacks. CBS News, citing BleepingComputer, notes some later tests demonstrated successful remote code execution.

That distinction matters, the Fact Check Team stresses: evidence that attackers have exploited a vulnerability does not establish that every vulnerable website was compromised or that customer information was stolen.

Determining whether data was accessed requires investigating individual systems for signs of unauthorized activity.

What administrators should do now

The bottom line per CBS News: the flaws are serious, fixes are available and exploitation has been documented — but whether a particular company was breached depends on its own circumstances.

PHP administrators should identify affected installations and apply the security updates immediately, prioritizing systems accessible from the internet.

Organizations should work with web-hosting providers, check for PHP installations used by third-party applications and review system logs for suspicious activity — the third-party angle JD Supra highlights for risk teams.

Systems that cannot be updated promptly should follow official guidance to reduce exposure. Federal civilian agencies face a CISA remediation deadline, and CISA encourages other organizations to prioritize the fixes as well.

Sources

  1. cbs4local.com › Fact Check Team: Is the programming language 'PHP2Shell' putting websites at risk?
  2. jdsupra.com › Attack Attempts Preceded the PHP2Shell Patch: What It Means for Third-Party Risk | JD Supra

More on Programming