<?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>gHacks Technology News &#124; Latest Tech News, Software And Tutorials &#187; wordpress password</title> <atom:link href="http://www.ghacks.net/tag/wordpress-password/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Sat, 11 Feb 2012 21:54:04 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/> <item><title>WordPress 2.8.4 Security Update</title><link>http://www.ghacks.net/2009/08/12/wordpress-2-8-4-security-update/</link> <comments>http://www.ghacks.net/2009/08/12/wordpress-2-8-4-security-update/#comments</comments> <pubDate>Wed, 12 Aug 2009 08:10:57 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[The Web]]></category> <category><![CDATA[blog]]></category> <category><![CDATA[wordpress]]></category> <category><![CDATA[wordpress exploit]]></category> <category><![CDATA[wordpress password]]></category> <category><![CDATA[wordpress vulnerability]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=15268</guid> <description><![CDATA[We noticed a security vulnerability in WordPress 2.8.3 yesterday (and earlier versions as well) that allowed an attacker to reset passwords of users. While this vulnerability could not be exploited to gain access to the user account (unless access to the email account the password was send to was available as well) it could be [...]]]></description> <content:encoded><![CDATA[<p><img
src="http://www.ghacks.net/wp-content/uploads/2009/04/wordpress.png" alt="wordpress" title="wordpress" width="128" height="128" class="alignleft size-full wp-image-11834" />We <a
href="http://www.ghacks.net/2009/08/11/wordpress-remote-admin-password-reset-vulnerability/">noticed</a> a security vulnerability in WordPress 2.8.3 yesterday (and earlier versions as well) that allowed an attacker to reset passwords of users. While this vulnerability could not be exploited to gain access to the user account (unless access to the email account the password was send to was available as well) it could be used to annoy those users especially when combined with an automated script that would reset the password every seconds or minutes.</p><p>A fix was released with the announcement of the vulnerability which consisted of one line of code that had to be edited in the wp-login.php file of the WordPress installation. WordPress installations with the fix are safe from these kinds of attacks.</p><p><span
id="more-15268"></span>The WordPress team has nevertheless released WordPress 2.8.4. as a response to the security vulnerability. The new release patches this vulnerability and is a recommended update for every WordPress installation. The WordPress developers are providing additional information about the vulnerability in the announcement post as well.</p><p>It was only possible to reset a password of the first user account without a key according to this post which usually is the admin account of the WordPress installation. WordPress is not showing the new version in its interface. This may change in the next hours.</p><p>WordPress admins should head over to the WordPress website to <a
href="http://wordpress.org/news/2009/08/2-8-4-security-release/">download</a> the new version as of now.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2009/08/12/wordpress-2-8-4-security-update/feed/</wfw:commentRss> <slash:comments>8</slash:comments> </item> </channel> </rss>
