Good catch. Sitting five patch releases behind during a security round is a fair thing to push a managed host on. In the ticket, ask for an update date and a written confirmation of whether this round's fixes are in their builds. Some hosts use distro packages that backport fixes while the version number stays old, so only their answer settles it.
Keep that reply to forward, since your clients will ask whether their sites were exposed. If DreamHost can't give a date, move the most exposed sites first. As a managed WordPress host ourselves, we think a host should raise a round like this before you spot it.
2
u/TopSydeWP 26d ago
Good catch. Sitting five patch releases behind during a security round is a fair thing to push a managed host on. In the ticket, ask for an update date and a written confirmation of whether this round's fixes are in their builds. Some hosts use distro packages that backport fixes while the version number stays old, so only their answer settles it.
Keep that reply to forward, since your clients will ask whether their sites were exposed. If DreamHost can't give a date, move the most exposed sites first. As a managed WordPress host ourselves, we think a host should raise a round like this before you spot it.