At this moment in time, the workaround is to update the mod_security2-mlogc manually with the following command and then run the update process through WHM.

yum update mod_security2-mlogc