Totally, but in terms of readability for proof on concept, I can see why the author chose PHP. I think the repo was more for showing the vulnerability rather than an actual tool that could be used right out the box.

He is probably a relatively inexperienced programmer. But who cares? The main accomplishment / item on display here is the identification of a vulnerability in a high-value target (supposedly - I haven't verified it), not the PoC.

It's a proof-of-concept.

Also, PHP does have support for multiple threads and/or forking. It's just not commonly used.

[sigh]

Yes, I know PHP can use a standard fork() call. But if you fork, then you need to shard the attack space into different sections, and then pull all the results back together again. Or you manually use `split` on the wordlist and run them as parallel processes. Either way, you are going to have to go through that trouble to re-combining everything. At which point, you might as well use an actual threaded language.

(The only other way I know to do threading in PHP is with curl's multi-request feature, which is hacky and leads to several problems, in addition to head-of-line blocking).

I really think you are missing the point here. And why are you so exasperated? Take a break man.

pthreads. You know them?

You now know the payload and the endpoint, so feel feel to fork

POC's tend to be very spartan, the simplest thing that works is enough, the goal was to show that is possible not to release an effective burteforcing platform. Also last time I've checked nothing stopping you from running multiple PHP instances on the same server, or say load this to you 300,000 strong bot net ;)

This explains these days everyone and anyone is trying to find vulns even if their technical skills are limited to PHP.

Oh man, it's a PoC, not something to actively help script-kiddies crack Apple authentication! This isn't MEANT to be polished. This is meant to shame Apple into fixing their glaring security vulnerability.