I also tested the user's attachment against 5.1.0.Final, 5.1.1.Final, and 5.0.10.Final and none of those builds have this issue. This is only observed with the 5.2.x release stream.