Cloudflare Deploys WAF Protections for PHP’s php2shell Vulnerabilities

· Original article ↗

Summary

Cloudflare says its WAF protections for CVE-2026-109618 and CVE-2026-109619 are deployed across plans. Its new full transaction detection analyzes request and response signals; customers should still patch PHP.

Key points

  • Cloudflare says its WAF rules for CVE-2026-109618 and CVE-2026-109619 were deployed before public disclosure and protect customers with WAF enabled.
  • The vulnerabilities affect PHP 5.4 and later and may allow denial of service, data exposure, or remote code execution through specially crafted HTTP requests.
  • Cloudflare’s full transaction detection analyzes request and origin-response signals within one HTTP transaction, aiming to identify exploits with fewer false positives.
  • Cloudflare reports observing attack traffic and payload variations targeting customers; it says analysts will continue updating protections.
  • Cloudflare recommends updating PHP despite the WAF protections; code or plugin updates alone do not fix the runtime vulnerabilities.
  • A later update describes related CVE-2026-115560 in PHP’s session upload progress feature. The WAF protection applies when the default upload progress field name is used; customers who changed it are not covered by that rule.

Article Details

Event Type
Cloudflare deployed WAF protections for the PHP vulnerabilities known as php2shell, CVE-2026-109618 and CVE-2026-109619, after reporting that it observed attack traffic targeting its customers.
Impact
The vulnerabilities may allow denial of service, remote code execution, or sensitive data exposure on affected PHP servers. Cloudflare said its WAF protections were deployed automatically for customers using the WAF, but they do not replace updating PHP. Protection for the related CVE-2026-115560 is limited to sites using PHP's default upload progress field name.

MITRE ATT&CK

CVE

Vendors

Products

Related Articles