"parse error. not well formed"
I’m hoping Google users will find this post if they search for the following Windows Live Writer error message:
An unexpected error has occurred while attempting to log in:
Blog Server Error – Server Error -32700 Occurred
parse error. not well formed
A malformed XML-RPC request can cause this error, but I don’t know of any way that can happen with Windows Live Writer 2008 Final. A more likely and sinister cause is what Gordon Dewis discovered:
Googling wordpress.net.in revealed a number of pages, including a blog entry by Avice De’vereux that described the symptoms and said they were caused by a spam injection hijack by wordpress.net.in. I think the hijack was supposed to insert ads in the page footers, but I don’t recall seeing anything there.
The solution seems to be to replace the modified files with fresh copies from WordPress.org and harden your WP install from future attacks.
It’s not clear to me how the files are getting modified in the first place. Are there malicious themes/plugins that are trojans, or is there an exploitable hole in WP or PHP? Most of the users who reported this to me lately have been on WP 2.3.2, the latest. If you have more information, please comment or pingback… thanks!
(In case there are client implementers who are reading this, another way to get some WP installations to cause this error is to create very large XML-RPC requests, such as those containing large Base64-encoded images, and format the XML without any line breaks. Under some versions of PHP you’ll get the error. The solution is to add line breaks.)
Filed under: Windows Live Writer, WordPress | 11 Comments