Re: IL and XSS vulnerabilities in multiple themes for WordPress

["MustLive" <mustlive () websecurity com ua>]

Hi Shyaam!

Yes, developers should not pushed such vulns in the final code - not
mistakenly, not intentionally.

> In this case: the very name test.php

Such things happens and I also saw many times when particularly admins of
web sites or web developers (such as design studios) mistakenly left such
files as test.php (with phpinfo) at working web sites. But it's about
unintentional cases.

This is exactly intentional case. Developers of WooThemes intentionally
added this test.php file with holes into their commercial themes to allow
users of their themes to make "debugging". I.e. they have added additional
(and holed) feature and did it officially (because it's mentioned in
changelog) many years ago into many if not all their themes.

As it can be found in changelog for Live Wire
(http://demo.woothemes.com/wp-content/themes/livewire/changelog.txt) and
many other themes. Here is a quote:

2008.08.06 - Version 1.1

* includes/test.php - Added phpinfo() file for debugging resizer on buggy
hosts

So from 2008 in this and many other (if not all) their themes there is such
additional feature - with Information Leakage and Cross-Site Scripting
holes, in addition to all those holes which I wrote earlier. After I've
found this information in changelog, I saw that it's intentional. And it's
not first case when I see some web developers intentionally adding
php-scripts with phpinfo - and adding IL and XSS holes - it's because they
are not aware about the risks.

WooThemes themes are commercial ones, so I've not bought any of them and I'm
not using them. And like in case of previous holes in 89 their themes, I've
found these holes on sites in Internet (in those indexed by Google). I've
found only 15 affected themes from all WooThemes WordPress themes - only in
those which were indexed by Google - and there can be other their themes
with these vulnerabilities.

Best wishes & regards,
MustLive
Administrator of Websecurity web site
http://websecurity.com.ua

----- Original Message ----- 
From: "Shyaam" <shyaam () gmail com>
To: "MustLive" <mustlive () websecurity com ua>
Cc: <submissions () packetstormsecurity org>;
<full-disclosure () lists grok org uk>
Sent: Saturday, June 04, 2011 7:34 PM
Subject: Re: [Full-disclosure] IL and XSS vulnerabilities in multiple themes
for WordPress


Background: As long as developers are taught about the limitations and
checks, more like checks and balances, they should be able to ensure that
this type of vuln is not pushed out in the final code.

In this case: the very name test.php is indicative of the scenario where the
developers leave open backdoors for their testing purposes and forget to
remove them during a push for production. This is common in every industry.

On Jun 4, 2011, at 12:17 PM, "MustLive" <mustlive () websecurity com ua> wrote:

> Hello list!
>
> I want to warn you about Information Leakage and Cross-Site Scripting
> vulnerabilities in multiple themes for WordPress.
>
> -------------------------
> Affected products:
> -------------------------
>
> Vulnerable are the next themes by WooThemes: Live Wire (all three themes
> from Live Wire series), Gotham News, Typebased, Blogtheme, VibrantCMS,
> Fresh
> News, The Gazette Edition, NewsPress, The Station, The Original Premium
> News, Flash News, Busy Bee, Geometric. Other vulnerable themes for WP are
> possible.
>
> ----------
> Details:
> ----------
>
> In different themes there is test.php - script with phpinfo() - which
> leads
> to Information Leakage (disclosure of FPD and other important information
> about the server) and XSS (in PHP < 4.4.1, 4.4.3-4.4.6).
>
> Information Leakage (WASC-13):
>
> http://site/wp-content/themes/_theme's_name_/includes/test.php
>
> XSS (WASC-08):
>
> http://site/wp-content/themes/_theme's_name_/includes/test.php?a[]=%3Cscript%3Ealert(document.cookie)%3C/script%3E
>
> For Live Wire the script is placed at address
> http://site/wp-content/themes/livewire/includes/test.php, similarly for
> other themes.
>
> ------------
> Timeline:
> ------------
>
> 2011.04.11 - announced at my site.
> 2011.04.12 - informed developers.
> 2011.06.04 - disclosed at my site.
>
> These vulnerabilities are still not fixed by developers. So users of these
> themes are need to fix the vulnerabilities manually (e.g. by deleting of
> this script).
>
> I mentioned about these vulnerabilities at my site
> (http://websecurity.com.ua/5071/).
>
> Best wishes & regards,
> MustLive
> Administrator of Websecurity web site
> http://websecurity.com.ua
>
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/