<?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 bugs</title> <atom:link href="http://www.ghacks.net/tag/wordpress-bugs/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>Fri, 10 Feb 2012 20:51:26 +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.7.1 Update</title><link>http://www.ghacks.net/2009/02/11/wordpress-271-update/</link> <comments>http://www.ghacks.net/2009/02/11/wordpress-271-update/#comments</comments> <pubDate>Tue, 10 Feb 2009 22:59:07 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Software]]></category> <category><![CDATA[blog software]]></category> <category><![CDATA[wordpress]]></category> <category><![CDATA[wordpress blog]]></category> <category><![CDATA[wordpress bugs]]></category> <category><![CDATA[wordpress update]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=10460</guid> <description><![CDATA[Seems the WordPress developers have finally released a new version of the free blog software. The update to WordPress 2.7.1 (from 2.7) is a maintenance release which fixes 68 tickets. It is therefor a recommended upgrade and should be applied by WordPress webmasters as soon as possible. The WordPress tracker which is mentioned on the [...]]]></description> <content:encoded><![CDATA[<p>Seems the WordPress developers have finally released a new version of the free blog software. The update to WordPress 2.7.1 (from 2.7) is a maintenance release which fixes 68 tickets. It is therefor a recommended upgrade and should be applied by WordPress webmasters as soon as possible. The WordPress tracker which is mentioned on the update page is currently unavailable which is probably due to the release announcement which is visible for every admin in the WordPress interface.</p><p>You can download the latest version of <a
href="http://wordpress.org/news/2009/02/wordpress-271/">WordPress</a> from the official website or apply the upgrade manually in the WordPress interface. You can take a look at in depth file changes by following this link or at the 68 tickets that have been closed <a
href="http://core.trac.wordpress.org/query?status=closed&amp;milestone=2.7.1&amp;resolution=fixed&amp;order=priority">here</a>.</p><p>The update includes six tickets with a high rating and more than 50 rated as normal. While the update does not list many security fixes it is still recommended to update as soon as possible. The update will not alter the database and should not break anything including plugins or themes.</p><p><span
id="more-10460"></span></p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2009/02/11/wordpress-271-update/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>WordPress Incorrect Password</title><link>http://www.ghacks.net/2007/12/01/wordpress-incorrect-password/</link> <comments>http://www.ghacks.net/2007/12/01/wordpress-incorrect-password/#comments</comments> <pubDate>Sat, 01 Dec 2007 09:10:09 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Knowledge]]></category> <category><![CDATA[The Web]]></category> <category><![CDATA[wordpress]]></category> <category><![CDATA[wordpress bugs]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2007/12/01/wordpress-incorrect-password/</guid> <description><![CDATA[Cheryl emailed me this morning telling me that her password would not be accepted by Wordpress after registering a new account although she was sure that she did type it correctly. The message that would appear was always "Incorrect Password". My first step of solving this problem was to change the password to "test" and try the login procedure again.]]></description> <content:encoded><![CDATA[<p>Cheryl emailed me this morning telling me that her password would not be accepted by WordPress after registering a new account although she was sure that she did type it correctly. The message that would appear was always &#8220;Incorrect Password&#8221;. My first step of solving this problem was to change the password to &#8220;test&#8221; and try the login procedure again.</p><p>This did not work as well and the Incorrect Password screen did appear again. I then tried to generate a new password but this was also not accepted. I headed out and performed some searches for a solution and finally found it.</p><p>It seems that WordPress is having problems with upper case usernames. Cheryl registered her account with a upper case C. I deleted that account, registered again with cheryl as the username instead and et voila, I was able to login immediately with the password that was send to my email address.</p><p><span
id="more-2104"></span>This will hopefully help all the other users who use upper case letters in their WordPress usernames only to find out that login in with them does not work.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2007/12/01/wordpress-incorrect-password/feed/</wfw:commentRss> <slash:comments>3</slash:comments> </item> <item><title>Secure WordPress with the first WordPress Worm</title><link>http://www.ghacks.net/2007/08/02/secure-wordpress-with-the-first-wordpress-worm/</link> <comments>http://www.ghacks.net/2007/08/02/secure-wordpress-with-the-first-wordpress-worm/#comments</comments> <pubDate>Thu, 02 Aug 2007 15:57:18 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Tools]]></category> <category><![CDATA[security vulnerabilities]]></category> <category><![CDATA[wordpress bugs]]></category> <category><![CDATA[wordpress exploits]]></category> <category><![CDATA[wordpress patch]]></category> <guid
isPermaLink="false">http://www.ghacks.net/2007/08/02/secure-wordpress-with-the-first-wordpress-worm/</guid> <description><![CDATA[Did you know that the latest version of Wordpress contains at least seven security vulnerabilities that could compromise your blog ? If you use Wordpress you should make sure that to fix them as soon as possible. The easiest way to fix them right now is to use the first Wordpress worm - which is a good one - to fix all seven vulnerabilities for you.]]></description> <content:encoded><![CDATA[<p>Did you know that the latest version of WordPress contains at least seven security vulnerabilities that could compromise your blog ? If you use WordPress you should make sure that to fix them as soon as possible. The easiest way to fix them right now is to use the first WordPress worm &#8211; which is a good one &#8211; to fix all seven vulnerabilities for you.</p><p>The process requires some faith that the xss worm is really fixing the vulnerabilities but the application itself is easy. About the faith: I have not read negative reviews so far and the worm has been released two days ago which should be enough time for some experts to complain about it.</p><p>If you want to secure your blog you simply write a comment on your own blog while you are logged in as the administrator linking to http://mybeni.rootzilla.de/mybeNi/ ; Click on that link from your admin panel afterwards which will lead to the site.</p><p><span
id="more-1825"></span>The first page explains what will be done and only if you actively click on &#8220;Secure my Blog&#8221; the vulnerability scan will be started. It will check three WordPress files for the vulnerabilities and offer to fix them if the vulnerability is found.</p><p>The vulnerabilities can only be fixed if the files are writable so make sure they are. An alternative would be to copy the code that will be inserted and add it manually in the files. The complete code of the file is shown and the addition is highlighted.</p><p>I suggest to run the worm a second time to make sure that your blog is safe and that the fixes have been applied.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2007/08/02/secure-wordpress-with-the-first-wordpress-worm/feed/</wfw:commentRss> <slash:comments>8</slash:comments> </item> </channel> </rss>
