<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>Weblogtoolscollection News Topic: Server path disclosure in WP themes</title>
<link>http://weblogtoolscollection.com/news/</link>
<description>Weblogtoolscollection News Topic: Server path disclosure in WP themes</description>
<language>en</language>
<pubDate>Tue, 21 May 2013 08:56:48 +0000</pubDate>

<item>
<title>Truden on "Server path disclosure in WP themes"</title>
<link>http://weblogtoolscollection.com/news/topic/server-path-disclosure-in-wp-themes#post-1264</link>
<pubDate>Fri, 06 Jul 2007 10:48:33 +0000</pubDate>
<dc:creator>Truden</dc:creator>
<guid isPermaLink="false">1264@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;I see that Mark has taken in consideration the server path disclosure and he fixed it in this web site without tempering with the server settings.&#60;/p&#62;
&#60;p&#62;It would be nice of him if he explain to his readers how he did it and what is the risk if you do not do it.
&#60;/p&#62;</description>
</item>
<item>
<title>Truden on "Server path disclosure in WP themes"</title>
<link>http://weblogtoolscollection.com/news/topic/server-path-disclosure-in-wp-themes#post-1136</link>
<pubDate>Tue, 12 Jun 2007 22:54:38 +0000</pubDate>
<dc:creator>Truden</dc:creator>
<guid isPermaLink="false">1136@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;Oh, I know that it is a GLOBAL thing, but blogging system like WordPress should take care of its users.&#60;br /&#62;
&#60;strong&#62;It is rule:&#60;/strong&#62; Do all possible to secure your code and software.&#60;br /&#62;
If you can not do it, you must bring it to the attention of your users and I don't understand why news discussing security and anti spam issues are kept silently covered until they disappear in the time???
&#60;/p&#62;</description>
</item>
<item>
<title>polyxena on "Server path disclosure in WP themes"</title>
<link>http://weblogtoolscollection.com/news/topic/server-path-disclosure-in-wp-themes#post-1128</link>
<pubDate>Tue, 12 Jun 2007 15:36:56 +0000</pubDate>
<dc:creator>polyxena</dc:creator>
<guid isPermaLink="false">1128@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;This depends on the level of error reporting (set by hosting company and/or php.ini). Production sites really should suppress all errors/warnings, so it's a global thing, not just a WP thing
&#60;/p&#62;</description>
</item>
<item>
<title>Truden on "Server path disclosure in WP themes"</title>
<link>http://weblogtoolscollection.com/news/topic/server-path-disclosure-in-wp-themes#post-1117</link>
<pubDate>Mon, 11 Jun 2007 07:23:47 +0000</pubDate>
<dc:creator>Truden</dc:creator>
<guid isPermaLink="false">1117@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;I see that no one takes this problem as a serious security threat and weblogtoolscollection.com is not afraid to show its server path.&#60;/p&#62;
&#60;p&#62;Well, just in case you don't like to be so brave, you can use an .htaccess to cover this hole.&#60;br /&#62;
Put in the file this code:&#60;/p&#62;
&#60;p&#62;&#60;code&#62;&#38;lt;Files &#34;*.php&#34;&#38;gt;&#60;br /&#62;
Order allow,deny&#60;br /&#62;
Deny from all&#60;br /&#62;
&#38;lt;/Files&#38;gt;&#60;/code&#62;&#60;/p&#62;
&#60;p&#62;Upload this .htaccess file in all your theme directories.
&#60;/p&#62;</description>
</item>
<item>
<title>Truden on "Server path disclosure in WP themes"</title>
<link>http://weblogtoolscollection.com/news/topic/server-path-disclosure-in-wp-themes#post-1113</link>
<pubDate>Sat, 09 Jun 2007 16:52:29 +0000</pubDate>
<dc:creator>Truden</dc:creator>
<guid isPermaLink="false">1113@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;He-he :-)&#60;br /&#62;
I was doing some carpentry when a thought popped up in my mind:&#60;br /&#62;
what if you type in the address bar the path to your theme directory / index.php&#60;/p&#62;
&#60;p&#62;How do we secure theme/index.php???&#60;/p&#62;
&#60;p&#62;Not very clever designed template hook ;)&#60;br /&#62;
Or perhaps that is not a BIG problem and my ignorance is making me wary too much. :(
&#60;/p&#62;</description>
</item>
<item>
<title>Truden on "Server path disclosure in WP themes"</title>
<link>http://weblogtoolscollection.com/news/topic/server-path-disclosure-in-wp-themes#post-1112</link>
<pubDate>Sat, 09 Jun 2007 13:37:22 +0000</pubDate>
<dc:creator>Truden</dc:creator>
<guid isPermaLink="false">1112@http://weblogtoolscollection.com/news/</guid>
<description>&#60;p&#62;Server path disclosure is a serious hole jeopardizing your security.&#60;/p&#62;
&#60;p&#62;All theme developers should secure the theme files which are not supposed  to be called directly.&#60;/p&#62;
&#60;p&#62;It is very easy to find the path to your theme folder and then just call searchform.php or single.php or any other file which is used as included theme file.&#60;br /&#62;
By doing that you would see something like:&#60;/p&#62;
&#60;p&#62;Fatal error: Call to undefined function: bloginfo() in /var/www/myhost/mysite/docs/wp-content/themes/mytheme/searchform.php on line 2&#60;/p&#62;
&#60;p&#62;If a hacker needs your server path he/she has it.
&#60;/p&#62;</description>
</item>

</channel>
</rss>