This was also fixed in 5.2.5, but it wasn't listed as a fix version.