CVCOVANewsComputing, Opportunities, Value & Analysis
Cybersecurity & Privacy3 min read

Cloudflare challenges hackers to bypass its WAF in a CTF built around the "php2shell" PHP flaws

After a week the company describes as historic for security, Cloudflare is putting its web application firewall to the test with a challenge open to researchers on HackerOne. The goal is to capture a secret file on a deliberately vulnerable PHP server.

By COVA News newsroom
Cloudflare challenges hackers to bypass its WAF in a CTF built around the "php2shell" PHP flaws

Cloudflare has a file hidden on a server, and it wants someone to find it. More precisely, it wants a security researcher to pull off what its web application firewall (WAF, the filter that blocks malicious traffic before it reaches a site) is supposed to prevent. The company has launched the Cloudflare PHP Capture the Flag, a challenge built into its Bug Bounty program on HackerOne.

The announcement follows what the company itself calls a week for the history books of Internet security. According to its blog, eight eMudhra intermediate certificates were compromised first, opening the door to forged certificates that could be used to impersonate servers. Then came php2shell, a set of serious vulnerabilities in PHP, the language that powers much of the Web. Cloudflare says it shipped client updates and several mitigations, added rules to its WAF to block exploitation of the PHP flaws, and introduced a feature called full transaction detection. All of it was made available on every plan, including the free one.

A server that's vulnerable on purpose

The challenge centers on CVE-2026-109618 and CVE-2026-109619, the two vulnerabilities behind php2shell. The target is an installation of PHP 8.5.11 with standard extensions, Apache 2 (via mod_php) and an empty index.php, all running inside a Cloudflare container with the WAF's default rules enabled. The environment contains a file named /flag, and the system resets every few minutes, flag included.

The mission is to bypass the WAF, achieve remote code execution and retrieve the contents of /flag. Participants must then verify it in the challenge interface and submit a private report on HackerOne with "PHP CTF" in the title, including the full, reproducible exploit chain. Out of scope are file reads without code execution, local-only testing and rediscovery of the already known vulnerabilities. To qualify for a reward, the method must be materially different: changing the encoding doesn't count, and only the first complete, reproducible report will be considered.

The rules of engagement are strict. Participants must register on HackerOne and accept its terms, and they may only test the challenge domain's /php/* endpoints using POST. Cloudflare logs metadata and payloads from the tests, so it asks participants to use test data only. The company also reserves the right to end the challenge at any time.

The post itself stresses that the WAF is no substitute for patching. Blocking responses can keep exposed data from reaching an attacker, but it doesn't undo whatever has already been executed on the origin server. Anyone running PHP should follow the project's security advisories and update.

The blog doesn't specify the reward amounts or a closing date. For those working in security in Latin America, participation is open to anyone with a HackerOne account; it's worth checking the program page to see whether the challenge is still active before getting started.

Source: Cloudflare

Related news

Cybersecurity & Privacy

An official Microsoft package stole credentials on PyPI: what to check if you use AI agents

Two versions of Microsoft's agent-framework reached PyPI carrying a credential stealer, one day after Google warned of attackers using AI to exploit flaws without human intervention. Here is what development and IT teams in Latin America should check right now.

Cybersecurity & Privacy

Microsoft and FAA outages, FBI and USDA breaches: no evidence of a coordinated attack

Over nine days, service outages and alleged intrusions coincided in the United States, and social media buzzed with talk of a “cyber pandemic.” The evidence points to separate technical failures. The proven danger for users is something else: fake emails that use the outages as bait.

Cybersecurity & Privacy

Nginx: two critical HTTP/2 flaws expose millions of servers; here's how to check and protect yours

F5 has fixed two vulnerabilities in Nginx that allow an attacker to take control of a server without a username or password. Public proof-of-concept code is already circulating. This guide explains how to tell whether your server is at risk, which version to update to and what to do while you wait for your system's patch.