<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>TechBanyan &#187; wordpress security</title>
	<atom:link href="http://www.techbanyan.com/tag/wordpress-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.techbanyan.com</link>
	<description>American Trends</description>
	<lastBuildDate>Sat, 20 Mar 2010 18:23:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Wordpress Blog Hacked? Now What</title>
		<link>http://www.techbanyan.com/264/wordpress-blog-hacked-now-what/</link>
		<comments>http://www.techbanyan.com/264/wordpress-blog-hacked-now-what/#comments</comments>
		<pubDate>Tue, 15 Apr 2008 00:06:50 +0000</pubDate>
		<dc:creator>Troy</dc:creator>
				<category><![CDATA[Blogging]]></category>
		<category><![CDATA[Hacking]]></category>
		<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[hacking wordpress]]></category>
		<category><![CDATA[how to protect your website]]></category>
		<category><![CDATA[wordpress hack]]></category>
		<category><![CDATA[wordpress security]]></category>

		<guid isPermaLink="false">http://www.techbanyan.com/?p=264</guid>
		<description><![CDATA[
If you still have the old version of Wordpress deployed, remember your site can be easily hacked because of known exploits. The hackers may or may not have a lot to gain by injecting malware or spammy links on your website but if you own the website, it could be your worst nightmare.
A spammed website [...]]]></description>
		<wfw:commentRss>http://www.techbanyan.com/264/wordpress-blog-hacked-now-what/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Fixing Potential Privacy Breach In Collaborative Wordpress</title>
		<link>http://www.techbanyan.com/191/fixing-potential-privacy-breach-in-collaborative-wordpress-platform/</link>
		<comments>http://www.techbanyan.com/191/fixing-potential-privacy-breach-in-collaborative-wordpress-platform/#comments</comments>
		<pubDate>Fri, 22 Feb 2008 00:54:21 +0000</pubDate>
		<dc:creator>Troy</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[how to disable comments]]></category>
		<category><![CDATA[how to disable ipaddresses]]></category>
		<category><![CDATA[wordpress comments hiding]]></category>
		<category><![CDATA[wordpress ip addresses]]></category>
		<category><![CDATA[wordpress privacy issues]]></category>
		<category><![CDATA[wordpress security]]></category>
		<category><![CDATA[wordpress security issues]]></category>

		<guid isPermaLink="false">http://www.techbanyan.com/archives/191</guid>
		<description><![CDATA[
If you are the only one to login into the dashboard of a Wordpress run website, then its one less issue to worry about. But if you allow readers to register themselves as Contributors on the site and write posts, or have multiple users login into the admin panel, then there are chances of compromising [...]]]></description>
		<wfw:commentRss>http://www.techbanyan.com/191/fixing-potential-privacy-breach-in-collaborative-wordpress-platform/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
