> That was at least part of the story for the recent PHP issue.
For a widely known exploit effecting all versions of PHP, they can do this but I don't think they can do this for unique or just less wide reaching security vulnerabilities. While some inspection could be done and rules could exist to flag up potential attacks (I have seen this suggested), I think this might be part of a solution but this was still just conditional rules filtering these requests, I don't think we could produce programmatic rules to filter for exploits in a crappy web app or even an expensive AI model (I would imagine WAF will never be able to run a lot of the traffic though even fairly small AI models as they will cost too much for most applications per a packet).
That means we're going to be leaning on a 3rd party solution such as Cloudflare's security suite. That was at least part of the story for the recent PHP issue.