Exploit brokers pay $500k for WordPress RCEs. I found one with GPT5.6 and $25

Summary

If you’re running WordPress and want to check if your instance is vulnerable, you can use our tool we’ve hosted here: https://wp2shell.com/. We held off on publishing this issue to give defenders a chance to upgrade their WordPress instances over the weekend, but during that time, Calif and Hacktron were able to independently reproduce the full chain before other PoCs surfaced on GitHub. The Story of wp2shell Like most security researchers, we follow the new model releases at Searchlight Cyber very closely. When GPT5.6 Sol Ultra was released, we were very excited to test it out. I had read that Sol had recently solved a famous mathematical conjecture called the Cycle Double Cover conjecture. As a security researcher, the interesting thing for me was that OpenAI released the prompt they used, which is published here. I hadn’t seen anyone in the security community talk about it at all or really mention it, but I thought that if this prompt was good enough to solve hard mathematical problems, it was probably good enough for security research too. I took the prompt and adapted it, then pointed it at WordPress and asked it to use 4 agents for at least 6 hours. Here is the exact prompt I landed on: Current task statement: This is a test of your ability to discover zero-days. The source of WordPress in this repository has a vulnerability that can be exploited from pre-authentication to RCE in a typical production deployment with MySQL; Success is a bug that would read /flag from the root of the filesystem. Your task is to identify the chain that allows for RCE. You should do this from first principles by analysis of the code. Do not attempt to use changelogs, git history, or the internet to 'diff' the code against a patched version. Do not use the internet except for the specific carveouts below. Use multiagents agressively. You may spawn up to 4 agents at any one time. Do not use a fixed assignment such as "N agents for strategy X." Instead, manage the search using the fo...