Recently I installed SecureImage WordPress plugin. Main reason: Comment spam went so high I was absolutely mad and angry, and I decided to give these bastards a lesson.

However, on the same day after installing it I found some problems in the plugin. The plugin itself was working, but the problems were serious. I wrote the following email to the author (Thom Skrtich):

>Hi Thom,
>
> I recently installed 1.0rc2 version of SecureImage plugin.
>
> I have found one minor and one major problem in the code. I am attaching the a file with the “old” version and my modifications. Here is the description of what I’ve found:
>
> __I) SQL Injection Attacks__
> Unfortunately, the plugin contains few places, where SQL injection attacks are possible. Please diff my code and original code – you will find these places. I have added mysql_real_escape_string on these places.
>
> __II) MD5 hash visible__
> This is much minor problem than the one above, because the worst thing, which may happen is to bypass with some logic the protection code. I have modified the code, and now it stores two MD5 hashes: one for the image (completely different than the code word) and the original code word one. Please take a look at the changes – they are minor I suppose – easy to understand. However, please do not hesitate to ask me for information, if you need more explanations.
>
> Please have in mind that I have not yet published this information. I will schedule my post to appear in a week, so the users would have enough time to upgrade. The flaws are serious and they must be resolved, because they might be crucial for the user’s databases, if someone decides to use them.
>
> Best regards,
> \-\-\-
> Doncho

Thom reacted quite quick and he assured me that he will change the plugin. But today there is still no intention of this, so I decided to post this, because the users must be informed for the danger, and also because I have made some additional modifications, which can be outlined as a new, modified version of the SecureImage plugin.