<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WP Contact-Form Vulnerabilities</title>
	<atom:link href="http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/feed" rel="self" type="application/rss+xml" />
	<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities</link>
	<description>Always something worth reading...</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:09:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jim</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-14176</link>
		<dc:creator>Jim</dc:creator>
		<pubDate>Tue, 07 Oct 2008 14:46:16 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-14176</guid>
		<description>Just create a page with your contact information. Make a special gmail email account just for your blog and let-er rip. I am really starting to stay away from plugins because of all these security issues. Look at joomla, nearly every plugin has some sort of security issue with it, wordpress to follow.</description>
		<content:encoded><![CDATA[<p>Just create a page with your contact information. Make a special gmail email account just for your blog and let-er rip. I am really starting to stay away from plugins because of all these security issues. Look at joomla, nearly every plugin has some sort of security issue with it, wordpress to follow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-13152</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Tue, 26 Aug 2008 20:39:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-13152</guid>
		<description>Douglas.

When I&#039;ll find time I&#039;ll write you recommendations about these holes.

Guys.

As I wrote above I found holes in three contact form plugins. All contact form plugins (like any other plugins) can have holes. So it&#039;s better to attend to security and make security audit of all plugins and the whole sites.</description>
		<content:encoded><![CDATA[<p>Douglas.</p>
<p>When I&#8217;ll find time I&#8217;ll write you recommendations about these holes.</p>
<p>Guys.</p>
<p>As I wrote above I found holes in three contact form plugins. All contact form plugins (like any other plugins) can have holes. So it&#8217;s better to attend to security and make security audit of all plugins and the whole sites.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-13077</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Sun, 24 Aug 2008 21:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-13077</guid>
		<description>And don&#039;t forget about XSS holes in WP-ContactForm 1.5 (&lt;a href=&quot;http://websecurity.com.ua/948/&quot; rel=&quot;nofollow&quot;&gt;http://websecurity.com.ua/948/&lt;/a&gt;) and Contact Form ][ (&lt;a href=&quot;http://websecurity.com.ua/2328/&quot; rel=&quot;nofollow&quot;&gt;http://websecurity.com.ua/2328/&lt;/a&gt;) which are exist at contact form page. They can be used as for attacking admin and registered users of the site, as for attacking visitors of the site.</description>
		<content:encoded><![CDATA[<p>And don&#8217;t forget about XSS holes in WP-ContactForm 1.5 (<a href="http://websecurity.com.ua/948/" rel="nofollow">http://websecurity.com.ua/948/</a>) and Contact Form ][ (<a href="http://websecurity.com.ua/2328/" rel="nofollow">http://websecurity.com.ua/2328/</a>) which are exist at contact form page. They can be used as for attacking admin and registered users of the site, as for attacking visitors of the site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-13076</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Sun, 24 Aug 2008 21:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-13076</guid>
		<description>David, and once more about your post :-).
&lt;blockquote&gt;The actual contact form page that your users see is not vulnerable to these attacks.&lt;/blockquote&gt;
It&#039;s not correct statement. Because actual contact form page is vulnerable too - in both WP-ContactForm and Contact Form ][ plguins.

Abuse of Functionality hole in both plugins (which is working at the contact page) allow to send spam to arbitrary emails via sites with any of these plugins.

Insufficient Anti-automation hole in WP-ContactForm (due captcha bypass) allow to send any amount of messages to admin (and to any email in case of Abuse of Functionality hole). Insufficient Anti-automation in Contact Form ][ (due lack of captcha) also allow to send any amount of messages to admin (and to any email in case of Abuse of Functionality hole). In both case Insufficient Anti-automation hole is at the contact page.

Only Cross-Site Request Forgery and Cross-Site Scripting holes in both plugins are exist at options page (options-contactform.php). But even in these case there some persistent XSS there which can be used to attack visitors of site at contact page form. So there are a lot of holes in both of these plugins (like in original WP-ContactForm 1.5).</description>
		<content:encoded><![CDATA[<p>David, and once more about your post :-).</p>
<blockquote><p>The actual contact form page that your users see is not vulnerable to these attacks.</p></blockquote>
<p>It&#8217;s not correct statement. Because actual contact form page is vulnerable too &#8211; in both WP-ContactForm and Contact Form ][ plguins.</p>
<p>Abuse of Functionality hole in both plugins (which is working at the contact page) allow to send spam to arbitrary emails via sites with any of these plugins.</p>
<p>Insufficient Anti-automation hole in WP-ContactForm (due captcha bypass) allow to send any amount of messages to admin (and to any email in case of Abuse of Functionality hole). Insufficient Anti-automation in Contact Form ][ (due lack of captcha) also allow to send any amount of messages to admin (and to any email in case of Abuse of Functionality hole). In both case Insufficient Anti-automation hole is at the contact page.</p>
<p>Only Cross-Site Request Forgery and Cross-Site Scripting holes in both plugins are exist at options page (options-contactform.php). But even in these case there some persistent XSS there which can be used to attack visitors of site at contact page form. So there are a lot of holes in both of these plugins (like in original WP-ContactForm 1.5).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MustLive</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-13071</link>
		<dc:creator>MustLive</dc:creator>
		<pubDate>Sun, 24 Aug 2008 20:58:14 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-13071</guid>
		<description>David!

You wrote incorrect link ;-) (this link cab be written in another post about 2nd WP plugin if you want to write about it).

The post where you linked is about vulnerabilities in Contact Form ][. I wrote about vulnerability in WP-ContactForm in other post: http://websecurity.com.ua/2335/ (and I wrote about many other holes in WP-ContactForm last year in MoBiC project).

These are similar plugins (Contact Form ][ and WP-ContactForm) and they both have vulnerabilities. Contact Form ][ made by  Chip Cuccio and WP-ContactForm made by Douglas Karr - they both made from original WP-ContactForm 1.5 and both have made similar holes (and some holes left from original), but also have their own holes. And both these plugins need to improve their security.</description>
		<content:encoded><![CDATA[<p>David!</p>
<p>You wrote incorrect link ;-) (this link cab be written in another post about 2nd WP plugin if you want to write about it).</p>
<p>The post where you linked is about vulnerabilities in Contact Form ][. I wrote about vulnerability in WP-ContactForm in other post: <a href="http://websecurity.com.ua/2335/" rel="nofollow">http://websecurity.com.ua/2335/</a> (and I wrote about many other holes in WP-ContactForm last year in MoBiC project).</p>
<p>These are similar plugins (Contact Form ][ and WP-ContactForm) and they both have vulnerabilities. Contact Form ][ made by  Chip Cuccio and WP-ContactForm made by Douglas Karr - they both made from original WP-ContactForm 1.5 and both have made similar holes (and some holes left from original), but also have their own holes. And both these plugins need to improve their security.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Clark</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-12928</link>
		<dc:creator>Michael Clark</dc:creator>
		<pubDate>Wed, 20 Aug 2008 18:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-12928</guid>
		<description>Isn&#039;t this another case where locking down your wp-admin folder so only specific users can access it would be useful? Thesea ren&#039;t WP users, but users defined in a .htaccess file.</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t this another case where locking down your wp-admin folder so only specific users can access it would be useful? Thesea ren&#8217;t WP users, but users defined in a .htaccess file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hombrelobo</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-12919</link>
		<dc:creator>hombrelobo</dc:creator>
		<pubDate>Wed, 20 Aug 2008 07:10:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-12919</guid>
		<description>Would be nice to suggest a better one instead of saying there are millons better ones .... a link maybe ?</description>
		<content:encoded><![CDATA[<p>Would be nice to suggest a better one instead of saying there are millons better ones &#8230;. a link maybe ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: beliebtes Wordpress Plugin WP-ContactForm angreifbar &#187; Pixeldrama» Webdesign Berlin</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-12912</link>
		<dc:creator>beliebtes Wordpress Plugin WP-ContactForm angreifbar &#187; Pixeldrama» Webdesign Berlin</dc:creator>
		<pubDate>Mon, 18 Aug 2008 08:54:05 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-12912</guid>
		<description>[...] Quelle: perun &#124; Infos: BlogSecurity [...]</description>
		<content:encoded><![CDATA[<p>[...] Quelle: perun | Infos: BlogSecurity [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Schweizer WordPress Magazin &#187; Beitrag: Effektive Sicherheit in WordPress</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-12906</link>
		<dc:creator>Schweizer WordPress Magazin &#187; Beitrag: Effektive Sicherheit in WordPress</dc:creator>
		<pubDate>Sat, 16 Aug 2008 14:43:38 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-12906</guid>
		<description>[...] stammt von BlogSecurity, wo regelmässig auch Sicherheitslücken von WordPress und dessen Plugins (WP Contact Form Plugin) aufgedeckt werden. Um das eigene Blog zu scannen, muss lediglich dieser Kommentar in die [...]</description>
		<content:encoded><![CDATA[<p>[...] stammt von BlogSecurity, wo regelmässig auch Sicherheitslücken von WordPress und dessen Plugins (WP Contact Form Plugin) aufgedeckt werden. Um das eigene Blog zu scannen, muss lediglich dieser Kommentar in die [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WP-ContactForm mit Sicherheitsl</title>
		<link>http://blogsecurity.net/wordpress/wp-contact-form-vulnerabilities/comment-page-1#comment-12901</link>
		<dc:creator>WP-ContactForm mit Sicherheitsl</dc:creator>
		<pubDate>Thu, 14 Aug 2008 18:12:10 +0000</pubDate>
		<guid isPermaLink="false">http://blogsecurity.net/?p=263#comment-12901</guid>
		<description>[...] WordPress-Plugins f</description>
		<content:encoded><![CDATA[<p>[...] WordPress-Plugins f</p>
]]></content:encoded>
	</item>
</channel>
</rss>

