Daniel, we’ve just barely been made aware of this post. We are the web host in question here and I just wanted to let you know that there actually isn’t a Perl script involved here in any way. This customer’s site is simply using the CGI version of PHP. (We used a .cgi name on the php binary just to help us not confuse it with the CLI binary on our server.)
The format of the error might have also thrown you… as this isn’t the default Apache 500 error page. Our server has been configured to redirect 500 errors to an error handler that displays the script path and error message so that our hosting customers do not have to search for this information in the logs.
In short, this is a fairly standard WordPress implementation and uses suexec to run WordPress under our customer’s user id.
