<?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>Portfolio Archives -</title>
	<atom:link href="https://cvtfradio.net/category/portfolio/feed/" rel="self" type="application/rss+xml" />
	<link>https://cvtfradio.net/category/portfolio/</link>
	<description>Conscious Vibrations from terra firma radio</description>
	<lastBuildDate>Tue, 08 May 2018 21:15:21 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>WordPress 4.2.4 Security and Maintenance Release</title>
		<link>https://cvtfradio.net/2015/08/wordpress-4-2-4-security-and-maintenance-release/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-4-2-4-security-and-maintenance-release</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Tue, 04 Aug 2015 19:21:05 +0000</pubDate>
				<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Word Press]]></category>
		<category><![CDATA[WP Security and Maintenance Release]]></category>
		<guid isPermaLink="false">https://www.cvtfradio.net/?p=2920</guid>

					<description><![CDATA[<p>WordPress 4.2.4 Security and Maintenance Release  Posted August 4, 2015 by Samuel Sidler. Filed under Releases, Security. WordPress 4.2.4 is now available. This is a security release for all previous versions and we strongly encourage you to update your sites immediately. This release addresses six issues, including three cross-site scripting vulnerabilities and a potential SQL injection that [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2015/08/wordpress-4-2-4-security-and-maintenance-release/">WordPress 4.2.4 Security and Maintenance Release</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2 class="fancy"><span style="color: #ff6600;"><a style="color: #ff6600;" href="https://wordpress.org/news/2015/08/wordpress-4-2-4-security-and-maintenance-release/">WordPress 4.2.4 Security and Maintenance Release</a></span></h2>
<div class="meta"><img fetchpriority="high" decoding="async" class=" aligncenter" src="https://1.bp.blogspot.com/_wICHhTiQmrA/Sfg33R1tfZI/AAAAAAAADko/HM3HTRYJlQg/s1600/help1.PNG" alt="" width="754" height="397" /></div>
<div class="meta"></div>
<div class="meta"></div>
<div class="meta"> Posted August 4, 2015 by <a href="https://profiles.wordpress.org/samuelsidler">Samuel Sidler</a>. Filed under <a href="https://wordpress.org/news/category/releases/" rel="category tag">Releases</a>, <a href="https://wordpress.org/news/category/security/" rel="category tag">Security</a>.</div>
<div class="storycontent">
<p>WordPress 4.2.4 is now available. This is a<strong> security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>
<p>This release addresses six issues, including three cross-site scripting vulnerabilities and a potential SQL injection that could be used to compromise a site, which were discovered by <a href="https://sucuri.net/">Marc-Alexandre Montpas</a> of Sucuri, <a href="https://helenhousandi.com/">Helen Hou-Sandí</a> of the WordPress security team, <a href="https://www.checkpoint.com/">Netanel Rubin</a> of Check Point, and <a href="https://hackerone.com/reactors08">Ivan Grigorov</a>. It also includes a fix for a potential timing side-channel attack, discovered by <a href="https://www.scrutinizer-ci.com/">Johannes Schmitt</a> of Scrutinizer, and prevents an attacker from locking a post from being edited, discovered by <a href="https://www.linkedin.com/in/symbiansymoh">Mohamed A. Baset</a>.</p>
<p>Our thanks to those who have practiced <a href="https://make.wordpress.org/core/handbook/testing/reporting-security-vulnerabilities/">responsible disclosure</a> of security issues.</p>
<p>WordPress 4.2.4 also fixes four bugs. For more information, see the <a href="https://codex.wordpress.org/Version_4.2.4">release notes</a> or consult the <a href="https://core.trac.wordpress.org/log/branches/4.2?rev=33573&amp;stop_rev=33396">list of changes</a>.</p>
<p><a href="https://wordpress.org/download/">Download WordPress 4.2.4</a> or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.2.4.</p>
<p><em>Already testing WordPress 4.3? The second release candidate is now available (<a href="https://wordpress.org/wordpress-4.3-RC2.zip">zip</a>) and it contains these fixes. For more on 4.3, see <a href="https://wordpress.org/news/2015/07/wordpress-4-3-release-candidate/">the RC 1 announcement post</a>.</em></p>
<div class="sharedaddy sd-sharing-enabled">
<div class="robots-nocontent sd-block sd-social sd-social-icon-text sd-sharing">
<h3 class="sd-title">Share this:</h3>
</div>
</div>
</div>
<p>The post <a href="https://cvtfradio.net/2015/08/wordpress-4-2-4-security-and-maintenance-release/">WordPress 4.2.4 Security and Maintenance Release</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Adding an Admin User to the WordPress Database via MySQL</title>
		<link>https://cvtfradio.net/2015/06/adding-an-admin-user-to-the-wordpress-database-via-mysql/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=adding-an-admin-user-to-the-wordpress-database-via-mysql</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Mon, 01 Jun 2015 18:10:06 +0000</pubDate>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[add user to dababase]]></category>
		<guid isPermaLink="false">https://www.cvtfradio.net/?p=2910</guid>

					<description><![CDATA[<p>How to Add an Admin User to the WordPress Database via MySQL &#160; &#160; &#160; &#160; &#160; &#160; Few days ago, we ran into an issue where a user’s site got hacked and their admin account was deleted from the database. This locked them out of their site without any other entry. We went in [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2015/06/adding-an-admin-user-to-the-wordpress-database-via-mysql/">Adding an Admin User to the WordPress Database via MySQL</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>How to Add an Admin User to the WordPress Database via MySQL</p>
<p><img decoding="async" class="alignleft" src="https://cdn4.wpbeginner.com/blogposts/wpusersinsert.gif" alt="wp-users insert phpmyadmin table" width="520" height="201" /></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Few days ago, we ran into an issue where a user’s site got hacked and their admin account was deleted from the database. This locked them out of their site without any other entry. We went in to the phpMyAdmin and created a new admin user to grant them access. In this article, we will show you a step by step guide on how to create an admin user in WordPress Database via MySQL.</p>
<p>Note: You should always make a backup of your database before performing any MySQL edits. This tutorial requires basic understanding of how phpMyAdmin works.</p>
<p>First, you need to login to phpMyAdmin and locate your WordPress database.</p>
<p>Once inside phpMyAdmin;</p>
<p>Once you are in, we will be making changes to the wp_users and wp_usermeta tables. Lets go ahead and click on wp_users table.</p>
<p>phpMyAdmin wp_users table</p>
<p>We need to insert our new admin user’s information, so click on the Insert tab like it shows in the image above. In the insert form, add the following:</p>
<p>ID – pick a number (in our example, we will use the number 4).<br />
user_login – insert the username you want to use to access the WordPress Dashboard.<br />
user_pass – add a password for this username. Make sure to select MD5 in the functions menu (Refer to the screenshot below).<br />
user_nicename – put a nickname or something else that you would like to refer yourself as.<br />
user_email – add the email you want to associate with this account.<br />
user_url – this would be the url to your website.<br />
user_registered – select the date/time for when this user is registered.<br />
user_status – set this to 0.<br />
display_name – put the name you like to display for this user on the site (it can be your user_nicename value as well).<br />
Click on the Go Button</p>
<p>The post <a href="https://cvtfradio.net/2015/06/adding-an-admin-user-to-the-wordpress-database-via-mysql/">Adding an Admin User to the WordPress Database via MySQL</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>WordPress 4.2.2 Security and Maintenance Release</title>
		<link>https://cvtfradio.net/2015/05/wordpress-4-2-2-security-and-maintenance-release/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-4-2-2-security-and-maintenance-release</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Tue, 12 May 2015 22:04:03 +0000</pubDate>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Word Press]]></category>
		<category><![CDATA[WordPress 4.2.2 Security and Maintenance Release]]></category>
		<guid isPermaLink="false">https://www.cvtfradio.net/?p=2885</guid>

					<description><![CDATA[<p>WordPress 4.2.2 Security and Maintenance Release Posted May 7, 2015 by Samuel Sidler. Filed under Releases, Security. WordPress 4.2.2 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately. Version 4.2.2 addresses two security issues: &#160; The Genericons icon font package, which [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2015/05/wordpress-4-2-2-security-and-maintenance-release/">WordPress 4.2.2 Security and Maintenance Release</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<h2 class="fancy"><a href="https://wordpress.org/news/2015/05/wordpress-4-2-2/">WordPress 4.2.2 Security and Maintenance Release</a></h2>
<p><a href="https://cvtfradio.net/wp-content/uploads/2015/05/WordPress-logo.jpg"><img decoding="async" class=" size-medium wp-image-2886 alignleft" src="https://cvtfradio.net/wp-content/uploads/2015/05/WordPress-logo-300x159.jpg" alt="WordPress-logo" width="300" height="159" srcset="https://cvtfradio.net/wp-content/uploads/2015/05/WordPress-logo-300x159.jpg 300w, https://cvtfradio.net/wp-content/uploads/2015/05/WordPress-logo.jpg 780w" sizes="(max-width: 300px) 100vw, 300px" /></a>Posted May 7, 2015 by <a href="https://samuelsidler.com/">Samuel Sidler</a>. Filed under <a href="https://wordpress.org/news/category/releases/" rel="category tag">Releases</a>, <a href="https://wordpress.org/news/category/security/" rel="category tag">Security</a>.</p>
<div class="storycontent">
<p>WordPress 4.2.2 is now available. This is a <strong>critical security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>
<p>Version 4.2.2 addresses two security issues:</p>
<p>&nbsp;</p>
<ul>
<li>The Genericons icon font package, which is used in a number of popular themes and plugins, contained an HTML file vulnerable to a cross-site scripting attack. All affected themes and plugins hosted on <a href="https://wordpress.org/">WordPress.org</a> (including the Twenty Fifteen default theme) have been updated today by the WordPress security team to address this issue by removing this nonessential file. To help protect other Genericons usage, WordPress 4.2.2 proactively scans the wp-content directory for this HTML file and removes it. Reported by Robert Abela of <a href="https://netsparker.com">Netsparker</a>.</li>
<li>WordPress versions 4.2 and earlier are affected by a <a href="https://wordpress.org/news/2015/04/wordpress-4-2-1/">critical cross-site scripting vulnerability</a>, which could enable anonymous users to compromise a site. WordPress 4.2.2 includes a comprehensive fix for this issue. Reported separately by Rice Adu and Tong Shi from Baidu[X-team].</li>
</ul>
<p>The release also includes hardening for a potential cross-site scripting vulnerability when using the visual editor. This issue was reported by Mahadev Subedi.</p>
<p>Our thanks to those who have practiced <a href="https://make.wordpress.org/core/handbook/reporting-security-vulnerabilities/">responsible disclosure</a> of security issues.</p>
<p>WordPress 4.2.2 also contains fixes for 13 bugs from 4.2. For more information, see the <a href="https://codex.wordpress.org/Version_4.2.2">release notes</a> or consult the <a href="https://core.trac.wordpress.org/log/branches/4.2?rev=32418&amp;stop_rev=32324">list of changes</a>.</p>
<p><a href="https://wordpress.org/download/">Download WordPress 4.2.2</a> or venture over to Dashboard → Updates and simply click “Update Now.” Sites that support automatic background updates are already beginning to update to WordPress 4.2.2.</p>
<p>Thanks to everyone who contributed to 4.2.2:</p>
</div>
<p>The post <a href="https://cvtfradio.net/2015/05/wordpress-4-2-2-security-and-maintenance-release/">WordPress 4.2.2 Security and Maintenance Release</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>WordPress 4.2.1 released new patch</title>
		<link>https://cvtfradio.net/2015/04/wordpress-4-2-1-released-new-patch/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-4-2-1-released-new-patch</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Mon, 27 Apr 2015 21:48:29 +0000</pubDate>
				<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Word Press]]></category>
		<guid isPermaLink="false">https://www.cvtfradio.net/?p=2364</guid>

					<description><![CDATA[<p>WordPress 4.2.1 Released to Patch Comment Exploit Vulnerability Sarah Gooding April 27, 2015 4 photo credit: Will Montague – cc This morning we reported on an XSS vulnerability in WordPress 4.2, 4.1.2, 4.1.1, and 3.9.3, which allows an attacker to compromise a site via its comments. The security team quickly patched the vulnerability and released [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2015/04/wordpress-4-2-1-released-new-patch/">WordPress 4.2.1 released new patch</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<article id="post-42873" class="entry post publish author-sarah post-42873 format-standard has-post-thumbnail category-news category-wordpressorg post_tag-security">
<header class="entry-header">
<h1 class="entry-title font-headlines">WordPress 4.2.1 Released to Patch Comment Exploit Vulnerability</h1>
<div class="entry-byline font-secondary"><span class="entry-author"><a class="url fn n" title="Posts by Sarah Gooding" href="https://wptavern.com/author/sarah" rel="author">Sarah Gooding</a></span> <time class="entry-published updated" title="Monday, April 27, 2015, 3:46 pm" datetime="2015-04-27T15:46:07-04:00">April 27, 2015</time> <a class="comments-link" href="https://wptavern.com/wordpress-4-2-1-released-to-patch-comment-exploit-vulnerability#comments">4</a></div>
</header>
<div class="entry-content">
<figure id="attachment_20655" class="wp-caption aligncenter"><a class="img-hyperlink" href="https://i2.wp.com/wptavern.com/wp-content/uploads/2014/04/security-release.jpg" rel="prettyPhoto[42873]"><img loading="lazy" decoding="async" class="size-full wp-image-20655" src="https://i2.wp.com/wptavern.com/wp-content/uploads/2014/04/security-release.jpg?resize=1024%2C505" alt="photo credit: Will Montague - cc" width="644" height="318" /></a><figcaption class="wp-caption-text font-secondary">photo credit: <a href="https://www.flickr.com/photos/willmontague/3813295674/">Will Montague</a> – <a href="https://creativecommons.org/licenses/by-nc/2.0/">cc</a></figcaption></figure>
<p>This morning we reported on an <a href="https://wptavern.com/zero-day-xss-vulnerability-in-wordpress-4-2-currently-being-patched" target="_blank">XSS vulnerability in WordPress 4.2</a>, 4.1.2, 4.1.1, and 3.9.3, which allows an attacker to compromise a site via its comments. The security team quickly patched the vulnerability and <a href="https://wordpress.org/news/2015/04/wordpress-4-2-1/" target="_blank">released 4.2.1</a> within hours of being notified.</p>
<p>WordPress’ official statement on the security issue:</p>
<blockquote><p>The WordPress team was made aware of a XSS issue a few hours ago that we will release an update for shortly. It is a core issue, but the number of sites vulnerable is much smaller than you may think because the vast majority of WordPress-powered sites run Akismet, which blocks this attack. When the fix is tested and ready in the coming hours WordPress users will receive an auto-update and should be safe and protected even if they don’t use Akismet.</p></blockquote>
<p>That auto-update is now being rolled out to sites where updates have not been disabled. If you are unsure of whether or not your site can perform automatic background updates, Gary Pendergast linked to the <a href="https://wordpress.org/plugins/background-update-tester/" target="_blank">Background Update Tester</a> plugin in the security release. This is a core-supported plugin that will check your site for background update compatibility and explain any issues.</p>
<p>Since <a href="https://wordpress.org/plugins/akismet/" target="_blank">Akismet</a> is active on more than a million websites, the number of affected users that were not protected is much smaller than it might have been otherwise.</p>
<p>WordPress 4.2.1 is a critical security release for a widely publicized vulnerability that you do not want to ignore. Users are advised to update immediately. The background update may already have hit your site. If not, you can update manually by navigating to Dashboard → Updates.</p>
</div>
</article>
<p>The post <a href="https://cvtfradio.net/2015/04/wordpress-4-2-1-released-new-patch/">WordPress 4.2.1 released new patch</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>WordPress Security Alert</title>
		<link>https://cvtfradio.net/2015/04/wordpress-security-alert/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-security-alert</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Mon, 13 Apr 2015 20:26:39 +0000</pubDate>
				<category><![CDATA[IT Industry]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Wordpress Security Alert]]></category>
		<guid isPermaLink="false">https://www.cvtfradio.net/?p=2271</guid>

					<description><![CDATA[<p>WordPress Security Alert &#8211; WP Super cache Credit: Wikipedia Upgrade immediately ITWorld&#124;April 8, 2015 Security firm Sucuri revealed on their blog this week that they had uncovered a persistent cross-site scripting vulnerability in the popular WordPress plugin WP Super Cache. The effects of this vulnerability can be severe as an attacker can potentially insert malicious code [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2015/04/wordpress-security-alert/">WordPress Security Alert</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<header>
<h1>WordPress Security Alert &#8211; WP Super cache</h1>
</header>
<figure class="hero-img"><img decoding="async" src="https://images.techhive.com/images/article/2015/04/three_surveillance_cameras-100577821-primary.idge.jpg" alt="three surveillance cameras" /><figcaption> Credit: <a href="https://www.google.com/url?sa=i&amp;rct=j&amp;q=&amp;esrc=s&amp;source=images&amp;cd=&amp;cad=rja&amp;uact=8&amp;ved=0CAMQjxw&amp;url=ht" target="_blank" rel="nofollow">Wikipedia</a> </figcaption></figure>
<section class="deck">
<h2>Upgrade immediately</h2>
</section>
<div class="byline">
<p class="dateline">ITWorld<span class="divider">|</span>April 8, 2015</p>
</div>
<section class="bodee">
<div id="drr-container">
<p>Security firm <a href="https://sucuri.net/" target="new">Sucuri</a> revealed on their <a href="https://blog.sucuri.net/2015/04/security-advisory-persistent-xss-in-wp-super-cache.html" target="new">blog this week</a> that they had uncovered a persistent <a href="https://en.wikipedia.org/wiki/Cross-site_scripting" target="new">cross-site scripting</a> vulnerability in the popular WordPress plugin<a href="https://wordpress.org/plugins/wp-super-cache/" target="new"> WP Super Cache</a>. The effects of this vulnerability can be severe as an attacker can potentially insert malicious code into WordPress pages without your knowledge. Anyone who has experienced this type of attack due to a plugin security flaw knows how difficult and time consuming remediation can be.</p>
<figure class="large "><img loading="lazy" decoding="async" src="https://images.techhive.com/images/article/2015/04/supercache1-100577816-large.idge.png" alt="supercache1" width="620" height="123" /> <small class="credit">Cypress North</small></figure>
<p>WP Super Cache is deployed across all of the WordPress sites we host in our data center, and for good reason. The excellent plugin dramatically boosts the performance of WordPress sites while simultaneously reducing load on the web servers. The code for this plugin is mature and stable, rarely requiring updates. That&#8217;s part of the reason why it&#8217;s trusted by over 7 million websites. It&#8217;s popularity makes this security flaw a big concern for site owners.</p>
<figure class="medium "><img loading="lazy" decoding="async" src="https://images.techhive.com/images/article/2015/04/supercache2-100577820-medium.idge.png" alt="supercache2" width="375" height="480" /> <small class="credit">Cypress North</small></figure>
<p>The update process is quick and easy so you should take the time to log in and click the update now link as soon as you&#8217;re able. If you&#8217;re fortunate enough to maintain your sites under a multi-site install you&#8217;ll be able to take care of this issue in one shot. Otherwise, like us, you&#8217;re stuck logging into each installation and manually updating each site like we spent all yesterday doing.</p>
<p>According to the blog post by <a href="https://blog.sucuri.net/author/marc" rel="author">Marc-Alexandre Montpas</a>:</p>
<blockquote><p>Using this vulnerability, an attacker using a carefully crafted query could insert malicious scripts to the plugin’s cached file listing page. As this page requires a valid nonce in order to be displayed, a successful exploitation would require the site’s administrator to have a look at that particular section, manually.</p></blockquote>
<p>The nonce requirement lowers the odds of the backdoor taking effect since the cached page gets purged periodically, but still, better safe than sorry. The scale of the vulnerable sites makes exploitation an inevitable event. Do your part to protect the web and get updating.</p>
</div>
</section>
<p>The post <a href="https://cvtfradio.net/2015/04/wordpress-security-alert/">WordPress Security Alert</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>WordPress 4.0.1 Security Release</title>
		<link>https://cvtfradio.net/2014/10/wordpress-4-0-1-security-release/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=wordpress-4-0-1-security-release</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Fri, 03 Oct 2014 09:54:13 +0000</pubDate>
				<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[WordPress 4.0.1 Security Release]]></category>
		<guid isPermaLink="false">http://spotlight.themerex.net/?p=1805</guid>

					<description><![CDATA[<p><img width="225" height="225" src="https://cvtfradio.net/wp-content/uploads/2014/10/wordpress.png" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" decoding="async" srcset="https://cvtfradio.net/wp-content/uploads/2014/10/wordpress.png 225w, https://cvtfradio.net/wp-content/uploads/2014/10/wordpress-150x150.png 150w, https://cvtfradio.net/wp-content/uploads/2014/10/wordpress-100x100.png 100w" sizes="(max-width: 225px) 100vw, 225px" /></p>
<p>Posted November 20, 2014 by Andrew Nacin. Filed under Releases, Security. WordPress 4.0.1 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately. Sites that support automatic background updates will be updated to WordPress 4.0.1 within the next few hours. If you [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2014/10/wordpress-4-0-1-security-release/">WordPress 4.0.1 Security Release</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img width="225" height="225" src="https://cvtfradio.net/wp-content/uploads/2014/10/wordpress.png" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" decoding="async" srcset="https://cvtfradio.net/wp-content/uploads/2014/10/wordpress.png 225w, https://cvtfradio.net/wp-content/uploads/2014/10/wordpress-150x150.png 150w, https://cvtfradio.net/wp-content/uploads/2014/10/wordpress-100x100.png 100w" sizes="(max-width: 225px) 100vw, 225px" /></p><div class="meta">Posted November 20, 2014 by <a href="https://nacin.com/">Andrew Nacin</a>. Filed under <a href="https://wordpress.org/news/category/releases/" rel="category tag">Releases</a>, <a href="https://wordpress.org/news/category/security/" rel="category tag">Security</a>.</div>
<div class="storycontent">
<p>WordPress 4.0.1 is now available. This is a <strong>critical security release</strong> for all previous versions and we strongly encourage you to update your sites immediately.</p>
<p>Sites that support automatic background updates will be updated to WordPress 4.0.1 within the next few hours.</p>
<p>If you are still on WordPress 3.9.2, 3.8.4, or 3.7.4, you will be updated to 3.9.3, 3.8.5, or 3.7.5 to keep everything secure.</p>
<p>(We don’t support older versions, so please update to 4.0.1 for the latest and greatest.)</p>
<p>WordPress versions 3.9.2 and earlier are affected by a critical cross-site scripting vulnerability, which could enable anonymous users to compromise a site. This was reported by <a href="https://klikki.fi/">Jouko Pynnonen</a>. This issue does not affect version 4.0, but version 4.0.1 does address these eight security issues:</p>
<ul>
<li>Three cross-site scripting issues that a contributor or author could use to compromise a site. Discovered by <a href="https://joncave.co.uk/">Jon Cave</a>, <a href="https://www.miqrogroove.com/">Robert Chapin</a>, and <a href="https://johnblackbourn.com/">John Blackbourn</a> of the WordPress security team.</li>
<li>A cross-site request forgery that could be used to trick a user into changing their password.</li>
<li>An issue that could lead to a denial of service when passwords are checked. Reported by <a href="https://www.behindthefirewalls.com/">Javier Nieto Arevalo</a> and <a href="https://www.devconsole.info/">Andres Rojas Guerrero</a>.</li>
<li>Additional protections for server-side request forgery attacks when WordPress makes HTTP requests. Reported by Ben Bidner (vortfu).</li>
<li>An extremely unlikely hash collision could allow a user’s account to be compromised, that also required that they haven’t logged in since 2008 (I wish I were kidding). Reported by <a href="https://david.dw-perspective.org.uk">David Anderson</a>.</li>
<li>WordPress now invalidates the links in a password reset email if the user remembers their password, logs in, and changes their email address. Reported separately by <a href="https://twitter.com/MomenBassel">Momen Bassel</a>, <a href="https://c0dehouse.blogspot.in/">Tanoy Bose</a>, and <a href="https://managewp.com/">Bojan Slavković of ManageWP</a>.</li>
</ul>
<p>Version 4.0.1 also fixes 23 bugs with 4.0, and we’ve made two hardening changes, including better validation of EXIF data we are extracting from uploaded photos. Reported by <a href="https://www.securesolutions.no/">Chris Andrè Dale</a>.</p>
<p>We appreciated the <a href="https://codex.wordpress.org/FAQ_Security">responsible disclosure</a> of these issues directly to our security team. For more information, see the <a href="https://codex.wordpress.org/Version_4.0.1">release notes</a> or consult the <a href="https://core.trac.wordpress.org/log/branches/4.0?rev=30475&amp;stop_rev=29710">list of changes</a>.</p>
<p><a href="https://wordpress.org/download/">Download WordPress 4.0.1</a> or venture over to <strong>Dashboard → Updates</strong> and simply click “Update Now”.</p>
<p><em>Already testing WordPress 4.1? The second beta is now available (<a href="https://wordpress.org/wordpress-4.1-beta2.zip">zip</a>) and it contains these security fixes. For more on 4.1, see <a href="https://wordpress.org/news/2014/11/wordpress-4-1-beta-1/">the beta 1 announcement post</a>.</em></p>
</div>
<p>The post <a href="https://cvtfradio.net/2014/10/wordpress-4-0-1-security-release/">WordPress 4.0.1 Security Release</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>New Zero-Day Vulnerability Discovered in TimThumb Script</title>
		<link>https://cvtfradio.net/2014/10/how-to-get-outstanding-urban-night-photographs/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=how-to-get-outstanding-urban-night-photographs</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Fri, 03 Oct 2014 09:51:21 +0000</pubDate>
				<category><![CDATA[Media]]></category>
		<category><![CDATA[Portfolio]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[New Zero-Day Vulnerability]]></category>
		<guid isPermaLink="false">http://spotlight.themerex.net/?p=1803</guid>

					<description><![CDATA[<p><img width="1016" height="471" src="https://cvtfradio.net/wp-content/uploads/2014/10/alert.jpg" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" decoding="async" srcset="https://cvtfradio.net/wp-content/uploads/2014/10/alert.jpg 1016w, https://cvtfradio.net/wp-content/uploads/2014/10/alert-300x139.jpg 300w" sizes="(max-width: 1016px) 100vw, 1016px" /></p>
<p>WordPress Security Alert: New Zero-Day Vulnerability Discovered in TimThumb Script Sarah Gooding June 25, 2014 20 photo credit: kama17 – cc Security vulnerabilities have plagued the TimThumb script for years. It is most commonly used in cropping, zooming and resizing images in WordPress themes. After the large scale attacks launched against the script a few [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2014/10/how-to-get-outstanding-urban-night-photographs/">New Zero-Day Vulnerability Discovered in TimThumb Script</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<header class="entry-header">
<h1 class="entry-title font-headlines">WordPress Security Alert: New Zero-Day Vulnerability Discovered in TimThumb Script</h1>
<div class="entry-byline font-secondary"><span class="entry-author"><a class="url fn n" title="Posts by Sarah Gooding" href="https://wptavern.com/author/sarah" rel="author">Sarah Gooding</a></span> <time class="entry-published updated" title="Wednesday, June 25, 2014, 2:48 pm" datetime="2014-06-25T14:48:35-05:00">June 25, 2014</time> <a class="comments-link" title="Comment on WordPress Security Alert: New Zero-Day Vulnerability Discovered in TimThumb Script" href="https://wptavern.com/wordpress-security-alert-new-zero-day-vulnerability-discovered-in-timthumb-script#comments">20</a></div>
</header>
<div class="entry-content">
<figure id="attachment_25334" class="wp-caption aligncenter" style="width: 719px; text-align: justify;"><figcaption class="wp-caption-text font-secondary">photo credit: <a href="https://www.flickr.com/photos/kama17/9279705214/">kama17</a> – <a href="https://creativecommons.org/licenses/by/2.0/">cc</a></figcaption></figure>
<p style="text-align: justify;">Security vulnerabilities have <a href="https://wptavern.com/timthumb-vulnerability-bites-another-victim" target="_blank">plagued</a> the <a href="https://timthumb.googlecode.com/svn/trunk/timthumb.php" target="_blank">TimThumb</a> script for years. It is most commonly used in cropping, zooming and resizing images in WordPress themes. After the <a href="https://blog.sucuri.net/2011/08/attacks-against-timthumb-php-in-the-wild-list-of-themes-and-plugins-being-scanned.html" target="_blank">large scale attacks</a> launched against the script a few years ago, one might think that theme and plugin developers would be less likely to continue building with it. However, this is not the case and many websites are again in danger, according to the exploit <a href="https://cxsecurity.com/issue/WLB-2014060134" target="_blank">disclosure</a> issued today.</p>
<p style="text-align: justify;">TimThumb 2.8.13 has a vulnerability with its “Webshot” feature that, when enabled, allows attackers to execute commands on a remote website. At this time there is no patch. Security experts at Sucuri <a href="https://blog.sucuri.net/2014/06/timthumb-webshot-code-execution-exploit-0-day.html" target="_blank">break down the threat</a> as follows: <strong>“With a simple command, an attacker can create, remove and modify any files on your server.”</strong></p>
<p style="text-align: justify;">Although the Webshot feature should be disabled by default, Sucuri recommends that you check your timthumb file to make sure it’s disabled. Search for “WEBSHOT_ENABLED” and verify that it’s set to “false,” as shown below:</p>
<div id="highlighter_314875" class="syntaxhighlighter nogutter taverncode " style="text-align: justify;">
<div class="lines">
<div class="line alt1">
<table>
<tbody>
<tr>
<td class="content"><code class="plain">define (‘WEBSHOT_ENABLED’, false);</code></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<p style="text-align: justify;">This vulnerability affects many WordPress themes, plugins, and third party components. According to the disclosure, all themes from <a href="https://themify.me/" target="_blank">Themify</a> utilize this script, as well as several plugins, including <a href="https://wordpress.org/plugins/wordpress-gallery-plugin/" target="_blank">WordPress Gallery Plugin</a> and the <a href="https://wordpress.org/plugins/igit-posts-slider-widget/" target="_blank">IGIT Posts Slider Widget</a>.</p>
<p style="text-align: justify;">It’s important to recognize that your theme or plugin may also use this script, even if it’s not listed in the disclosure. If you’ve ever lost an entire weekend fixing client sites that fell victim to TimThumb exploits, then you know that disabling the WebShot option is probably a good idea. This is a simple thing that you can do now to prevent your sites from getting hacked.</p>
<div id="better-author-bio-div">
<div class="better-author-bio-div-info"><img loading="lazy" decoding="async" id="grav-d12f506a8f9afba443178608fc9e2232-0" class="avatar avatar-60 photo grav-hashed grav-hijack" src="https://1.gravatar.com/avatar/d12f506a8f9afba443178608fc9e2232?s=60&amp;d=&amp;r=R" alt="" width="60" height="60" /></p>
<h4 class="font-headlines" style="text-align: justify;">Who is Sarah Gooding</h4>
<p class="better-author-bio-div-meta" style="text-align: justify;">Sarah Gooding is an Editorial Ninja at Audrey Capital. When not writing about WordPress, she enjoys baking, knitting, judging beer competitions and spending time with her Italian Greyhound.</p>
</div>
</div>
</div>
<p>The post <a href="https://cvtfradio.net/2014/10/how-to-get-outstanding-urban-night-photographs/">New Zero-Day Vulnerability Discovered in TimThumb Script</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Web Security Issues</title>
		<link>https://cvtfradio.net/2014/10/web-security-issues/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=web-security-issues</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Fri, 03 Oct 2014 09:49:57 +0000</pubDate>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Design]]></category>
		<category><![CDATA[Web Security]]></category>
		<category><![CDATA[Word Press]]></category>
		<category><![CDATA[Web Security Issues]]></category>
		<guid isPermaLink="false">http://spotlight.themerex.net/?p=1801</guid>

					<description><![CDATA[<p><img width="540" height="260" src="https://cvtfradio.net/wp-content/uploads/2014/10/ecryption.jpg" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" decoding="async" srcset="https://cvtfradio.net/wp-content/uploads/2014/10/ecryption.jpg 540w, https://cvtfradio.net/wp-content/uploads/2014/10/ecryption-300x144.jpg 300w" sizes="(max-width: 540px) 100vw, 540px" /></p>
<p>A serious vulnerability in the WP eCommerce Plugin was announced within the last 24 hours (321st Oct 2014) . A fix has been released and some hosting companies are already auto-upgrading customers to the newest version. Upgrade to 3.8.14.4 of WP eCommerce immediately if you use this plugin. Please spread the word because with almost [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2014/10/web-security-issues/">Web Security Issues</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<p><img width="540" height="260" src="https://cvtfradio.net/wp-content/uploads/2014/10/ecryption.jpg" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" decoding="async" srcset="https://cvtfradio.net/wp-content/uploads/2014/10/ecryption.jpg 540w, https://cvtfradio.net/wp-content/uploads/2014/10/ecryption-300x144.jpg 300w" sizes="(max-width: 540px) 100vw, 540px" /></p><p id="yui_3_16_0_1_1416864681517_48384">A serious vulnerability in the <a class="yiv4485711366valid-link yiv4485711366validation-enabled yiv4485711366validating" href="https://clicks.aweber.com/y/ct/?l=FLnrU&amp;m=3kDg7Km37O6aApy&amp;b=0ptQiJ6leDcIw2mMKUw6kg" target="_blank" rel="nofollow">WP eCommerce Plugin</a> was announced within the last 24 hours (321st Oct 2014) . A fix has been released and some hosting companies are already auto-upgrading customers to the newest version.</p>
<p id="yui_3_16_0_1_1416864681517_48387">Upgrade to 3.8.14.4 of WP eCommerce immediately if you use this plugin. Please spread the word because with almost 3 million downloads this is a very popular plugin.</p>
<p id="yui_3_16_0_1_1416864681517_48390"><strong id="yui_3_16_0_1_1416864681517_48389"><a id="yui_3_16_0_1_1416864681517_48388" class="yiv4485711366valid-link yiv4485711366validation-enabled yiv4485711366validating" href="https://clicks.aweber.com/y/ct/?l=FLnrU&amp;m=3kDg7Km37O6aApy&amp;b=lF4QGQud_ZQEoo5ZAytSMA" target="_blank" rel="nofollow">Details on our blog&#8230;</a></strong></p>
<p id="yui_3_16_0_1_1416864681517_48391"><strong>​</strong></p>
<p>The post <a href="https://cvtfradio.net/2014/10/web-security-issues/">Web Security Issues</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to upgrade to SSL certificates from SHA1 to SHA2</title>
		<link>https://cvtfradio.net/2014/10/upgrade-to-ssl-certificates-from-sha1-to-sha2/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=upgrade-to-ssl-certificates-from-sha1-to-sha2</link>
		
		<dc:creator><![CDATA[L3gsman]]></dc:creator>
		<pubDate>Fri, 03 Oct 2014 09:46:48 +0000</pubDate>
				<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Security]]></category>
		<guid isPermaLink="false">http://spotlight.themerex.net/?p=1795</guid>

					<description><![CDATA[<p><img width="327" height="157" src="https://cvtfradio.net/wp-content/uploads/2014/10/256bit.jpg" class="attachment-post-thumbnail size-post-thumbnail wp-post-image" alt="" decoding="async" srcset="https://cvtfradio.net/wp-content/uploads/2014/10/256bit.jpg 327w, https://cvtfradio.net/wp-content/uploads/2014/10/256bit-300x144.jpg 300w" sizes="(max-width: 327px) 100vw, 327px" /></p>
<p>With Chrome version 39 which is in the process of being released (see footnote), Google has started issuing warnings if a website is using a certificate that has a signature algorithm that uses the older and less secure SHA1. To find out which signature algorithm your secure website is using, in Chrome click on the green [&#8230;]</p>
<p>The post <a href="https://cvtfradio.net/2014/10/upgrade-to-ssl-certificates-from-sha1-to-sha2/">How to upgrade to SSL certificates from SHA1 to SHA2</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>With Chrome version 39 which is in the process of being released (see footnote), Google has started issuing warnings if a website is using a certificate that has a signature algorithm that uses the older and less secure SHA1.</p>
<p>To find out which signature algorithm your secure website is using, in Chrome click on the green lock in the location bar. Then click on ‘connection’, then click on ‘certificate information’. You should see something like the image below. Note the ‘Signature algorithm’ is SHA-256 which is one of the SHA2 hashing functions. If you see SHA-1, you need to immediately reissue your certificate using SHA-2 and install the new version.</p>
<p><a href="https://www.wordfence.com/blog/wp-content/uploads/2014/11/Screen-Shot-2014-11-21-at-7.53.10-PM.png"><img loading="lazy" decoding="async" class="alignnone size-medium wp-image-397" src="https://www.wordfence.com/blog/wp-content/uploads/2014/11/Screen-Shot-2014-11-21-at-7.53.10-PM-298x300.png" alt="Screen Shot 2014-11-21 at 7.53.10 PM" width="298" height="300" /></a></p>
<p>So what does it look like in the new version of Chrome when you’re using SHA-1? This is taken from a well known website that has not upgraded yet. Notice the lock with the warning triangle in the location bar. This is the main indication for a site visitor that something is awry. If you then click on the lock it has a further warning with explanation.</p>
<p><a href="https://www.wordfence.com/blog/wp-content/uploads/2014/11/Screen-Shot-2014-11-21-at-7.46.24-PM.png"><img loading="lazy" decoding="async" class="alignnone wp-image-398 " src="https://www.wordfence.com/blog/wp-content/uploads/2014/11/Screen-Shot-2014-11-21-at-7.46.24-PM-538x1024.png" alt="Screen Shot 2014-11-21 at 7.46.24 PM" width="326" height="620" /></a></p>
<p>If you do have a website that is using SHA-1, don’t panic. Just sign into GoDaddy or whoever your SSL issuer is. Then go to manage your certificates and they’ll have an option there to reissue your certificate. You’ll need to resubmit your certificate signing request (CSR) but you can just resubmit your old CSR and it will work fine.</p>
<p>Then make sure that you’ve selected SHA-2 or SHA-256 or another <a href="https://en.wikipedia.org/wiki/SHA-2">SHA-2 compatible function</a>. Then reissue the certificate. In GoDaddy’s case it takes about a minute for them to approve your request. If you have an EV certificate it may take longer.</p>
<p>Please share this with other site administrators to make sure that their customers aren’t getting warnings when visiting those all-important secure pages.</p>
<p><strong>Footnote</strong>: Chrome 39 has <a href="https://googlechromereleases.blogspot.com/2014/11/stable-channel-update_18.html">officially been pushed into the “Stable” channe</a>l which is the release channel. It will be pushed out via auto-update to millions of customers in the coming days. The demo above was done with Chrome 40 beta, but what the user sees is identical.</p>
<p>The post <a href="https://cvtfradio.net/2014/10/upgrade-to-ssl-certificates-from-sha1-to-sha2/">How to upgrade to SSL certificates from SHA1 to SHA2</a> appeared first on <a href="https://cvtfradio.net"></a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
