Within the last few days a number of remote SQL Injection vulnerablities within a variety of plugins have been released. This new search for this type of vulnerability follows David Kierznowski’s recent finding in the popular WP TextLinkAds plugin.

dmsguestbook 1.7.0 is vulnerable to multiple vulnerabilites. At first it’s possible to Deface your wp-config.php, an Attacker can gain in that way access to your MySQL data. It’s caused by improperly control/sanitization of the parameters folder & file. At the same time there are multiple XSS vulnerabilities which are also HIGH risk issues.

There are several SQL Injection vulnerabilities within this plugin. More information is available at bugtraq.

We highly recommend to disable and remove the plugin from your Blog until a major version release to address all these holes. It is likely that previous versions are affected as well.

The Version 1.8 is available but BlogSecurity have received reports that it does not solve all the problems.

st_newsletter 2.x is vulnerable to SQL Injection. This is caused by improper sanitisation of the newsletter parameter within the shiftthis-preview.php file. This makes it possible to retrieve a list of all registered Users and their Password hashes. This hole was discovered by S@BUN and we’re not aware of any current fixes.

Another SQL Injection was made public by S@BUN again, for Wordspew here is the parameter id in wordspew-rss.php. This parameter is not sanitized and therefore open to attacks. Again we’re not aware of any fixes.The latest version, 3.72 fixes the Vulnerability. It’s available on the official WordSpew Webpage

The last hole for now is within wp-footnotes 2.2. The current version allows access to the Adminpanel of the plugin via the URL. This results in XSS vulnerabilities. More can be found over on BugTraq. Again no fix is currently available.

Comments

DK on 5 February, 2008 at 10:40 am #

Again, as I stressed before, secure coding functions, documentation and procedures need to be in place before this gets better!


Pierre Sudarovich on 8 February, 2008 at 10:24 am #

Hi all,
ok the bug in wordspew-rss.php is now corrected ;)


BlogSecurity » Blog Archive » WordPress BlogWatch on 10 February, 2008 at 8:01 pm #

[...] SQL Injection Vulnerability (more) [...]


[...] array elements could execute unsanitized HTML to exploit the plugin. Other plugins with problems: WordsPew v3.x reported an “id” based SQL injection vulnerability, dmsguestbook 1.7.0, st_newsletter [...]


[...] array elements could execute unsanitized HTML to exploit the plugin. Other plugins with problems: WordsPew v3.x reported an “id” based SQL injection vulnerability, dmsguestbook 1.7.0, st_newsletter [...]


[...] Blogsecurity.net (an excellent security blog and well worth bookmarking) reported on the security flaws of some packages and poorly formed mySQL input. Note this isn’t malicious coding of plugins - it’s just code that hasn’t been checked thoroughly in its inputs. Still, the end result is someone gets access to something they shouldn’t. [...]


Comment
Name:
Email:
Website:
Message: