Cloudflare PHP CTF Tests WAF Defenses Against Two PHP Vulnerabilities
- Cargo
- Machine Learning
- Shipped
- Shipper
- Celso Martinho
- Readers
- 521
A HackerOne challenge invites researchers to test Cloudflare’s WAF against two PHP flaws, with rewards tied to distinct, reproducible bypasses.

Cloudflare has updated its web application firewall (WAF) protections for the PHP vulnerabilities behind php2shell and is inviting security researchers to test whether those defenses can be bypassed. The PHP Capture the Flag (CTF) challenge runs through Cloudflare’s HackerOne program. Participants must achieve remote code execution in a sandbox, retrieve a temporary flag, and document a distinct, reproducible WAF bypass to qualify for a reward.
Cloudflare says submissions have helped harden existing php2shell protections and create new detections. The challenge remains open, and researchers are encouraged to submit materially distinct bypasses. Managed rule changes are listed in the Cloudflare WAF changelog.
A controlled test of WAF protections
The challenge targets CVE-2026-109618 and CVE-2026-109619, the two PHP vulnerabilities associated with php2shell. Cloudflare has placed a deliberately vulnerable PHP environment behind its default WAF rules for these flaws. The setup uses stock PHP 8.5.11 with standard extensions, Apache 2 via mod_php, and an empty index.php, running inside a Cloudflare Container.
A file named /flag sits inside the sandbox. The environment, including the flag, resets every few minutes, so a successful exploit needs to retrieve and verify the current value before it changes. The challenge page at php-rce.cloudflare.app provides the environment details, scope, and verification form.
The exercise reflects a practical problem for defenders: protections need to be tested against real request patterns and bypass techniques as they emerge. Cloudflare says broader use of AI can help attackers find new vectors faster, making outside research useful for examining where current WAF assumptions hold and where they fail.
What counts as a qualifying submission
Participants must first create a HackerOne account and agree to the program’s terms and rules. To meet the challenge requirements, they must use an authorized POST request to run attacker-controlled PHP code or commands inside the sandbox, use that execution to recover /flag, and verify the flag through the challenge interface. Verification should happen promptly because resets invalidate the current flag; participants should retain the successful result for review.
Flag verification in the interface does not file a report or establish priority. Participants must also submit a private report to Cloudflare through HackerOne with “PHP CTF” in the title. The report needs the endpoint, full payload, request sequence, relevant headers, encoding and body bytes, plus raw request and response captures or a proof of concept that reproduces the exploit chain. It must explain how the WAF was bypassed, what code or command ran, and how execution recovered the flag. The report should include the attempt ID, verification result, and exploit and verification times in UTC. Cloudflare may also request the flag privately to confirm the result.
Rewards depend on a materially distinct WAF bypass method. Different PHP exploits, payloads, execution techniques, or flag-recovery steps do not make a submission unique when they rely on the same bypass mechanism. Equivalent encodings, new flags, resets, attempt IDs, and cosmetic edits also do not create a distinct method. The first complete, reproducible report is considered for equivalent submissions, including when the bypass has not yet been fixed; Cloudflare makes the final decisions about duplicates and rewards.
Several outcomes do not qualify: disclosing a file without demonstrating remote code execution, achieving execution without recovering and verifying the flag, local-only exploits, rediscovering the known PHP flaws, or reporting a detection difference or partial chain without completing the objective.
Scope and testing limits
Testing is authorized only on the challenge hostname’s WAF-protected /php/* endpoints, using POST requests. Direct access to the underlying infrastructure, other Cloudflare services, the upstream PHP project, and third-party systems is out of scope. Participants must not use denial-of-service methods, high-volume scanning, persistence, social engineering, or attacks against other participants. Requests that receive a 429 or 503 response should be paused.
Cloudflare records attempted metadata and request payloads to support its review of reports. Participants should use test data and avoid sending credentials, personal information, or other sensitive material. The company’s privacy notice describes its data practices. If the challenge description conflicts with the HackerOne bounty terms, those terms take precedence. Cloudflare can suspend or end the challenge at any time; its HackerOne page is the reference for current availability.
WAF rules do not replace PHP updates
A WAF can block some exploit requests and stop exposed data from reaching an attacker, but it cannot reverse actions that have already run on the server. Cloudflare advises PHP operators to follow the project’s security advisories and install relevant updates. The CTF offers a way to test one layer of defense under controlled conditions; patching remains necessary for fixing vulnerable software.
Researchers can access the sandbox at php-rce.cloudflare.app. The useful result for defenders will be the methods that reproduce reliably and reveal where WAF rules need to change.