<?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>Weblog Tools Collection &#187; rating</title>
	<atom:link href="http://weblogtoolscollection.com/archives/tag/rating/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblogtoolscollection.com</link>
	<description>Weblog Tools Blogging Tools Blog</description>
	<lastBuildDate>Tue, 14 Feb 2012 14:00:48 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Comment Rating Plugin Fixes Security Vulnerability</title>
		<link>http://weblogtoolscollection.com/archives/2010/12/08/comment-rating-plugin-fixes-security-vulnerability/</link>
		<comments>http://weblogtoolscollection.com/archives/2010/12/08/comment-rating-plugin-fixes-security-vulnerability/#comments</comments>
		<pubDate>Wed, 08 Dec 2010 20:00:30 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress Security]]></category>
		<category><![CDATA[comments]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[rating]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=9151</guid>
		<description><![CDATA[If you use the Comment Rating plugin for your WordPress powered site, you are highly encouraged to upgrade to the latest version as it fixes a security vulnerability. More specifically, a Cross-site Request Forgery attack. According to the report at OSVDB.org which is an Open Source Vulnerability Database: The flaw exists because the application does not require multiple steps or explicit confirmation for unspecified sensitive transactions for the admin function. By using a crafted URL (e.g., a crafted GET request inside an &#8220;img&#8221; tag), an attacker may trick the victim into clicking on the image to take advantage of the trust relationship between the authenticated victim and the application. Such an attack could trick the victim into executing arbitrary commands in the context of their session with the application, without further prompting or verification. There is no known workaround for versions lower than 2.9.21. Kudos goes to KrebsOnSecurity for reporting [...]]]></description>
			<content:encoded><![CDATA[<p>If you use the Comment Rating plugin for your WordPress powered site, you are highly encouraged to upgrade to the latest version as it <a href="http://wordpress.org/extend/plugins/comment-rating/changelog/">fixes a security vulnerability</a>. More specifically, a Cross-site Request Forgery attack. According to the report at OSVDB.org which is an Open Source Vulnerability Database:</p>
<blockquote><p>The flaw exists because the application does not require multiple steps or explicit confirmation for unspecified sensitive transactions for the admin function. By using a crafted URL (e.g., a crafted GET request inside an &#8220;img&#8221; tag), an attacker may trick the victim into clicking on the image to take advantage of the trust relationship between the authenticated victim and the application. Such an attack could trick the victim into executing arbitrary commands in the context of their session with the application, without further prompting or verification.</p></blockquote>
<p>There is no known workaround for versions lower than 2.9.21. Kudos goes to <a href="http://krebsonsecurity.com/">KrebsOnSecurity</a> for reporting the flaw and to <a href="http://profiles.wordpress.org/users/bobking/">bobking</a> who quickly published a new version with the patch.</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2010/12/08/comment-rating-plugin-fixes-security-vulnerability/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Are Your Theme Standards?</title>
		<link>http://weblogtoolscollection.com/archives/2009/05/18/what-are-your-theme-standards/</link>
		<comments>http://weblogtoolscollection.com/archives/2009/05/18/what-are-your-theme-standards/#comments</comments>
		<pubDate>Mon, 18 May 2009 20:30:02 +0000</pubDate>
		<dc:creator>Jeff Chandler</dc:creator>
				<category><![CDATA[WordPress Templates WordPress Skins WordPress Themes]]></category>
		<category><![CDATA[rating]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[system]]></category>
		<category><![CDATA[themes]]></category>

		<guid isPermaLink="false">http://weblogtoolscollection.com/?p=5867</guid>
		<description><![CDATA[On a thread within the WPTavern forum, there is an interesting discussion taking place among some prominent theme authors on creating a theme standards system. The initial idea is to create a standards system which would give theme authors a goal to shoot for. However, as the discussion has progressed, it&#8217;s easy to see that this entire idea of rating themes or putting together a set of standards is a complex problem. So after reading through that thread, I thought it would be a good idea to tap into the WordPress community to figure out what is most important to you when it comes to using a theme? Is it price, license, design, usability, functionality, or something else?]]></description>
			<content:encoded><![CDATA[<p>On a thread within the WPTavern forum, there is <a href="http://www.wptavern.com/forum/themes-templates/480-theme-standards-system.html">an interesting discussion</a> taking place among some prominent theme authors on creating a theme standards system. The initial idea is to create a standards system which would give theme authors a goal to shoot for. However, as the discussion has progressed, it&#8217;s easy to see that this entire idea of rating themes or putting together a set of standards is a complex problem. </p>
<p>So after reading through that thread, I thought it would be a good idea to tap into the WordPress community to figure out what is most important to you when it comes to using a theme? Is it price, license, design, usability, functionality, or something else?</p>
]]></content:encoded>
			<wfw:commentRss>http://weblogtoolscollection.com/archives/2009/05/18/what-are-your-theme-standards/feed/</wfw:commentRss>
		<slash:comments>27</slash:comments>
		</item>
	</channel>
</rss>
<!-- This Quick Cache file was built for (  weblogtoolscollection.com/archives/tag/rating/feed/ ) in 0.48418 seconds, on Feb 14th, 2012 at 5:42 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 14th, 2012 at 6:42 pm UTC -->
