Two things from the provider side, one of which is the boring answer
nobody likes.
On the pre-auth bugs specifically - the cPanel one Cantech mentions,
and the WHMCS ones - patching faster is not really the answer any more.
Mivocloud is right that the window between disclosure and mass scanning
has collapsed. By the time you read the advisory, the scanning is often
already running. The defence that still works is unglamorous: do not
let the management plane be reachable from the whole internet. WHM,
WHMCS admin, panel logins - behind an allowlist, behind a VPN, or at
minimum on a hostname that is not the one printed on every customer
invoice. A pre-auth RCE you cannot reach is not an incident.
Second, offered as context rather than advice: we do not run cPanel or
WHMCS, we built the console in house. The honest trade is that we gave
up an enormous amount of functionality and years of engineering to stay
out of a blast radius where one advisory exposes every host on the same
stack in the same second. For most people that is not a good trade -
the features are real and the engineering is not free. But it is worth
naming that "almost everyone runs the same two products" is itself part
of why these advisories hurt as much as they do.
On NiceNIC's point - a billing bug that surfaces at the next renewal
cron rather than at deploy is the nastiest shape this takes, because
the gap between shipping it and finding out is a full billing cycle.
The only test we trust for that is a real transaction on a real
schedule, not a staging run.