<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/MustLive Edition" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Коментарі для запису: Виконання коду в WordPress 2.5 - 3.1.1</title>
	<link>http://websecurity.com.ua/5108/</link>
	<description></description>
	<pubDate>Wed, 13 May 2026 18:22:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=MustLive Edition</generator>

	<item>
		<title>від: MustLive</title>
		<link>http://websecurity.com.ua/5108/#comment-364964</link>
		<pubDate>Sun, 03 Jul 2011 18:05:07 +0000</pubDate>
		<guid>http://websecurity.com.ua/5108/#comment-364964</guid>
					<description>&lt;strong&gt;Dear mac.&lt;/strong&gt;

The vulnerability, which I wrote in this post, is already fixed in WP 3.1.3. So these attackers used another hole in your WordPress or in plugin for WP or in other webapps or in web server.

If they attacked you via brute forcing ssh and they picked up password for root, then you need to change this password also, not only password for your WP installation. In any case, if you changed all passwords, but they still putting phishing content at your site, then it's quite possible that they put backdoor into site (in WP or in other webapps).

Concerning backdoor you can read in my article &lt;a href="http://websecurity.com.ua/4909/" rel="nofollow"&gt;Placing shells (backdoors) at web sites&lt;/a&gt;. So you need to find backdoor and delete it (or you can delete all files in your WP folder and reinstall WP and all plugins for it, to make "clean" installation).</description>
		<content:encoded><![CDATA[<p><strong>Dear mac.</strong></p>
<p>The vulnerability, which I wrote in this post, is already fixed in WP 3.1.3. So these attackers used another hole in your WordPress or in plugin for WP or in other webapps or in web server.</p>
<p>If they attacked you via brute forcing ssh and they picked up password for root, then you need to change this password also, not only password for your WP installation. In any case, if you changed all passwords, but they still putting phishing content at your site, then it&#8217;s quite possible that they put backdoor into site (in WP or in other webapps).</p>
<p>Concerning backdoor you can read in my article <a href="http://websecurity.com.ua/4909/" rel="nofollow">Placing shells (backdoors) at web sites</a>. So you need to find backdoor and delete it (or you can delete all files in your WP folder and reinstall WP and all plugins for it, to make &#8220;clean&#8221; installation).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>від: mac</title>
		<link>http://websecurity.com.ua/5108/#comment-364951</link>
		<pubDate>Sun, 03 Jul 2011 15:37:24 +0000</pubDate>
		<guid>http://websecurity.com.ua/5108/#comment-364951</guid>
					<description>Someone uploaded a phishing script to my latest worpress version 3.14

http://let.de/index.php/code-execution-vulnerability-in-wordpress/

what todo ?  :(  8O</description>
		<content:encoded><![CDATA[<p>Someone uploaded a phishing script to my latest worpress version 3.14</p>
<p><a href="http://let.de/index.php/code-execution-vulnerability-in-wordpress/" rel="nofollow">http://let.de/index.php/code-execution-vulnerability-in-wordpress/</a></p>
<p>what todo ?  <img src='http://websecurity.com.ua/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' />   <img src='http://websecurity.com.ua/wp-includes/images/smilies/icon_eek.gif' alt='8O' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>від: MustLive</title>
		<link>http://websecurity.com.ua/5108/#comment-360836</link>
		<pubDate>Sat, 28 May 2011 16:24:32 +0000</pubDate>
		<guid>http://websecurity.com.ua/5108/#comment-360836</guid>
					<description>В WordPress 3.1.3 розробники виправили дану уразливість. При цьому, традиційно, не подякувавши мені (ні публічно, ні приватно).</description>
		<content:encoded><![CDATA[<p>В WordPress 3.1.3 розробники виправили дану уразливість. При цьому, традиційно, не подякувавши мені (ні публічно, ні приватно).
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
