<?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>Website maintenance Archives - Tarheel Media</title>
	<atom:link href="https://tarheel.media/tag/website-maintenance/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Digital Marketing The Right Way</description>
	<lastBuildDate>Mon, 14 Sep 2026 16:53:32 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://tarheel.media/wp-content/uploads/2022/12/cropped-tarheel-icon-1-32x32.png</url>
	<title>Website maintenance Archives - Tarheel Media</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Urgent WP Fastest Cache Security Update: What Website Owners Need to Know</title>
		<link>https://tarheel.media/company-news/2026/09/14/wp-fastest-cache-security-update-2026/?pk_campaign=feed&#038;pk_kwd=wp-fastest-cache-security-update-2026</link>
		
		<dc:creator><![CDATA[Mike W.]]></dc:creator>
		<pubDate>Mon, 14 Sep 2026 16:53:32 +0000</pubDate>
				<category><![CDATA[Company News]]></category>
		<category><![CDATA[Security Bulletin]]></category>
		<category><![CDATA[Service Updates]]></category>
		<category><![CDATA[Cache Poisoning]]></category>
		<category><![CDATA[Cross-Site Scripting]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[Managed WordPress]]></category>
		<category><![CDATA[Plugin Updates]]></category>
		<category><![CDATA[Security Updates]]></category>
		<category><![CDATA[Website maintenance]]></category>
		<category><![CDATA[Website security]]></category>
		<category><![CDATA[Wordfence]]></category>
		<category><![CDATA[WordPress plugins]]></category>
		<category><![CDATA[WordPress security]]></category>
		<category><![CDATA[WP Fastest Cache]]></category>
		<category><![CDATA[XSS]]></category>
		<guid isPermaLink="false">https://tarheel.media/?p=8283</guid>

					<description><![CDATA[<p>Website owners using WP Fastest Cache should update immediately. Two recently disclosed vulnerabilities could allow attackers to manipulate cached pages or inject malicious scripts.</p>
<p>The post <a href="https://tarheel.media/company-news/2026/09/14/wp-fastest-cache-security-update-2026/?pk_campaign=feed&#038;pk_kwd=wp-fastest-cache-security-update-2026">Urgent WP Fastest Cache Security Update: What Website Owners Need to Know</a> appeared first on <a href="https://tarheel.media">Tarheel Media</a>.</p>
]]></description>
										<content:encoded><![CDATA[<h1>Urgent WP Fastest Cache Security Update</h1>
<p>A security update has been released for WP Fastest Cache, a popular WordPress caching plugin used on more than one million websites.</p>
<p>Website owners should update WP Fastest Cache to version 1.5.2 as soon as possible. Versions 1.5.0 and earlier contain two vulnerabilities that can potentially be exploited without an attacker having a WordPress account.</p>
<h2>What Was Discovered?</h2>
<p>The first vulnerability, identified as CVE-2026-74916, involves cache poisoning.</p>
<p>WP Fastest Cache could create a shared cached page from a request containing manipulated query-string parameters. That altered version could then be delivered to people visiting the normal website address.</p>
<p>This vulnerability affects WP Fastest Cache versions 0.8.7.7 through 1.5.0 and received a CVSS severity score of 6.1.</p>
<p>A second vulnerability, CVE-2026-19760, involves stored cross-site scripting, commonly called stored XSS.</p>
<p>Under certain configurations, an unauthenticated attacker could cause malicious JavaScript to be written into a website’s shared cache. That code could then execute when visitors or administrators opened the affected page.</p>
<p>This particular attack requires Polylang or Polylang Pro to be active while WP Fastest Cache’s Combine JS feature is enabled. It received a CVSS severity score of 7.2.</p>
<h2>What Could an Attacker Do?</h2>
<p>Depending on the website’s configuration and the vulnerability being exploited, an attacker could potentially:</p>
<ul>
<li>Display altered or fraudulent content</li>
<li>Redirect visitors to another website</li>
<li>Inject advertisements or SEO spam</li>
<li>Capture information entered into an affected page</li>
<li>Execute actions through a logged-in administrator’s browser</li>
<li>Damage the website’s reputation or search visibility</li>
</ul>
<p>These vulnerabilities do not automatically provide direct access to the server, database or hosting account. Receiving a vulnerability warning also does not mean that a website has already been compromised.</p>
<p>It does mean that affected installations should be updated promptly.</p>
<h2>Which Versions Are Affected?</h2>
<p>WP Fastest Cache 1.5.0 and earlier should be considered vulnerable.</p>
<p>Version 1.5.1 corrected the two publicly disclosed cache-poisoning and stored-XSS vulnerabilities. Version 1.5.2 includes those corrections along with additional security improvements and stronger permission checks for Varnish and page-specific cache-management functions.</p>
<p>As of September 14, 2026, website owners should update directly to version 1.5.2.</p>
<h2>What Website Owners Should Do</h2>
<p>Updating the plugin is only the first step. Because this vulnerability involves cached content, every applicable cache should also be purged.</p>
<p>Website owners and administrators should:</p>
<ol start="1">
<li>Create or verify a current website backup.</li>
<li>Update WP Fastest Cache to version 1.5.2.</li>
<li>Select “Delete Cache and Minified CSS/JS” from WP Fastest Cache.</li>
<li>Purge any Cloudflare, CDN, Varnish, proxy or hosting-level cache.</li>
<li>Run a complete Wordfence or comparable security scan.</li>
<li>Check the website for unfamiliar scripts, redirects, administrator accounts or modified files.</li>
</ol>
<p>Clearing every cache layer helps ensure that content created before the update is not still being delivered to visitors.</p>
<h2>Should You Assume Your Website Was Hacked?</h2>
<p>No. A vulnerable plugin is not the same thing as a confirmed compromise.</p>
<p>If the plugin is updated, every cache is cleared, the website scans clean and there are no unexplained redirects, administrator accounts or file changes, there is generally no reason to assume a breach occurred.</p>
<p>If suspicious behavior is discovered, the website should be treated as a possible security incident and examined before normal operation continues.</p>
<h2>Tarheel Media Can Help</h2>
<p>Keeping WordPress software updated is an essential part of maintaining a secure website. A firewall such as Wordfence can help block malicious traffic, but it does not replace installing security updates.</p>
<p>If you are uncertain whether your website uses WP Fastest Cache, which version is installed or whether every cache layer has been cleared, contact Tarheel Media for assistance.</p>
<p>Additional technical information is available through the <a href="https://wordpress.org/plugins/wp-fastest-cache/#developers">official WP Fastest Cache changelog</a>, <a href="https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/wp-fastest-cache/wp-fastest-cache-wordpress-cache-plugin-0877-150-unauthenticated-cache-poisoning">Wordfence’s cache-poisoning advisory</a> and <a href="https://www.wordfence.com/threat-intel/vulnerabilities/wordpress-plugins/wp-fastest-cache/wp-fastest-cache-150-unauthenticated-stored-cross-site-scripting-via-http-host-header">Wordfence’s stored-XSS advisory</a>.</p>
<img decoding="async" src="https://stats.tarheel.media/piwik.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Ftarheel.media%2Fcompany-news%2F2026%2F09%2F14%2Fwp-fastest-cache-security-update-2026%2F%3Fpk_campaign%3Dfeed%26pk_kwd%3Dwp-fastest-cache-security-update-2026&amp;action_name=Urgent%20WP%20Fastest%20Cache%20Security%20Update%3A%20What%20Website%20Owners%20Need%20to%20Know&amp;urlref=https%3A%2F%2Ftarheel.media%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" /><p>The post <a href="https://tarheel.media/company-news/2026/09/14/wp-fastest-cache-security-update-2026/?pk_campaign=feed&#038;pk_kwd=wp-fastest-cache-security-update-2026">Urgent WP Fastest Cache Security Update: What Website Owners Need to Know</a> appeared first on <a href="https://tarheel.media">Tarheel Media</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Service Changes for Hosting and Support</title>
		<link>https://tarheel.media/company-news/2026/09/13/service-changes-for-hosting-and-support/?pk_campaign=feed&#038;pk_kwd=service-changes-for-hosting-and-support</link>
		
		<dc:creator><![CDATA[Mike W.]]></dc:creator>
		<pubDate>Sun, 13 Sep 2026 16:50:06 +0000</pubDate>
				<category><![CDATA[Company News]]></category>
		<category><![CDATA[Service Updates]]></category>
		<category><![CDATA[content updates]]></category>
		<category><![CDATA[Customer Support]]></category>
		<category><![CDATA[hosting policy]]></category>
		<category><![CDATA[hosting support]]></category>
		<category><![CDATA[labor contracts]]></category>
		<category><![CDATA[managed hosting]]></category>
		<category><![CDATA[service changes]]></category>
		<category><![CDATA[support coverage]]></category>
		<category><![CDATA[support plans]]></category>
		<category><![CDATA[Tarheel Media]]></category>
		<category><![CDATA[technical support]]></category>
		<category><![CDATA[web hosting]]></category>
		<category><![CDATA[Website maintenance]]></category>
		<category><![CDATA[Website Management]]></category>
		<category><![CDATA[website support]]></category>
		<guid isPermaLink="false">https://tarheel.media/?p=8271</guid>

					<description><![CDATA[<p>Tarheel Media is changing how non-hosting support is provided to customers without an active website or support contract.</p>
<p>The post <a href="https://tarheel.media/company-news/2026/09/13/service-changes-for-hosting-and-support/?pk_campaign=feed&#038;pk_kwd=service-changes-for-hosting-and-support">Service Changes for Hosting and Support</a> appeared first on <a href="https://tarheel.media">Tarheel Media</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p data-pm-slice="1 1 []">Effective Monday, September 14, 2026, at 6:00 p.m. Eastern Time, Tarheel Media is changing how we provide content assistance, troubleshooting, research, and other professional services to customers with hosting-only accounts.</p>
<p>This change does not reduce or remove anyone’s website hosting. It establishes a clear distinction between website hosting and the professional labor required to modify, investigate, or manage a website.</p>
<h2>Why This Change Is Necessary</h2>
<p>Tarheel Media has historically provided a substantial amount of content assistance, troubleshooting, research, and other professional labor to customers who pay only for website hosting.</p>
<p>These requests have grown to more than 50 hours of unpaid labor each week. That is no longer sustainable while maintaining affordable hosting prices and providing dependable service to customers with active support agreements.</p>
<p>Hosting fees pay for the systems and infrastructure required to keep a website available. They do not include unlimited content changes, research, troubleshooting, configuration, design, or development unless those services are included in a separate written agreement.</p>
<h2>Who Is Affected?</h2>
<p>This change generally affects customers who:</p>
<ul data-spread="false">
<li>Pay only for monthly or annual website hosting</li>
<li>Do not have an active website, labor, maintenance, or support contract</li>
<li>Commonly pay less than $20 per month or less than $300 per year</li>
</ul>
<p>If you are paying less than these amounts, your account is generally a hosting-only account. Your written agreement and active services ultimately determine your coverage.</p>
<h2>Who Is Not Affected?</h2>
<p>Customers who are still making scheduled payments under an active website contract are not affected by this change.</p>
<p>Services for those customers will continue according to the scope and terms of their written agreements. Customers with an active support, labor, or maintenance agreement will also continue receiving the services covered by that agreement.</p>
<h2>How Non-Hosting Support Will Work</h2>
<p>Beginning after the effective time, customers without active support coverage must prepay for one hour of labor for each non-hosting support request.</p>
<p>Work will begin after the initial hour has been purchased. If the request requires more than one hour, additional time will be billed at the current rates published on our website.</p>
<p>When the scope can reasonably be determined before an investigation begins, we may provide an estimate. Some technical problems cannot be accurately estimated until they have been examined.</p>
<p>Examples of billable support include:</p>
<ul data-spread="false">
<li>Writing, changing, formatting, or uploading website content</li>
<li>Replacing images, documents, buttons, menus, or page elements</li>
<li>Design, layout, navigation, or functionality changes</li>
<li>Plugin, theme, application, or account configuration</li>
<li>Investigating website behavior or reproducing a reported problem</li>
<li>Troubleshooting third-party software, services, devices, or integrations</li>
<li>SEO, analytics, performance, or marketing research</li>
<li>Testing, implementation, development, training, or administrative assistance</li>
</ul>
<h2>What Hosting Continues to Cover</h2>
<p>This policy does not remove the hosting service you purchase. Features specifically included in your hosting plan will continue normally.</p>
<p>If a verified problem originates from Tarheel Media’s hosting infrastructure or another covered hosting system, we will investigate and correct that hosting-related problem according to your service terms.</p>
<p>A hosting failure is different from a request to modify content, investigate third-party software, configure a service, or diagnose a problem that does not originate from the hosting infrastructure.</p>
<h2>General Recommendations Remain Available</h2>
<p>We remain happy to provide brief general recommendations when they can be offered without research, account access, investigation, testing, or implementation.</p>
<p>When answering a question requires us to examine a particular website, account, configuration, data set, or reported problem, it becomes a support request.</p>
<h2>Adding a Support Contract</h2>
<p>Customers who regularly need content assistance, troubleshooting, research, maintenance, or other professional services can purchase a customized labor contract.</p>
<p>A support contract provides planned coverage without requiring a separate prepaid hour for every covered request.</p>
<p><a href="https://tarheel.media/store/contracts/customized-labor-contract/">Purchase a Customized Labor Contract</a></p>
<h2>Keeping Hosting Affordable and Support Sustainable</h2>
<p>We value every customer who entrusts a website to Tarheel Media. This change allows us to continue offering affordable hosting while ensuring that professional support work is properly scheduled and compensated.</p>
<p>If you are uncertain whether your account includes support coverage, contact us before submitting work. We will confirm your current coverage without charge.</p>
<img decoding="async" src="https://stats.tarheel.media/piwik.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Ftarheel.media%2Fcompany-news%2F2026%2F09%2F13%2Fservice-changes-for-hosting-and-support%2F%3Fpk_campaign%3Dfeed%26pk_kwd%3Dservice-changes-for-hosting-and-support&amp;action_name=Service%20Changes%20for%20Hosting%20and%20Support&amp;urlref=https%3A%2F%2Ftarheel.media%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" /><p>The post <a href="https://tarheel.media/company-news/2026/09/13/service-changes-for-hosting-and-support/?pk_campaign=feed&#038;pk_kwd=service-changes-for-hosting-and-support">Service Changes for Hosting and Support</a> appeared first on <a href="https://tarheel.media">Tarheel Media</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Outdated WordPress Plugins make 60,000 Websites Vulnerable</title>
		<link>https://tarheel.media/security-bulletin/2023/05/17/outdated-wordpress-plugins-make-60000-websites-vulnerable/?pk_campaign=feed&#038;pk_kwd=outdated-wordpress-plugins-make-60000-websites-vulnerable</link>
		
		<dc:creator><![CDATA[Michael Gilmore]]></dc:creator>
		<pubDate>Wed, 17 May 2023 18:27:20 +0000</pubDate>
				<category><![CDATA[Security Bulletin]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[Exploitable plugins]]></category>
		<category><![CDATA[Information system security]]></category>
		<category><![CDATA[Penetration testing]]></category>
		<category><![CDATA[Plugin vulnerabilities]]></category>
		<category><![CDATA[Remote code execution]]></category>
		<category><![CDATA[Security disclosure process]]></category>
		<category><![CDATA[Security research]]></category>
		<category><![CDATA[SQL injections]]></category>
		<category><![CDATA[Unauthorized access]]></category>
		<category><![CDATA[Vulnerable websites]]></category>
		<category><![CDATA[Website hijacking]]></category>
		<category><![CDATA[Website intrusions]]></category>
		<category><![CDATA[Website maintenance]]></category>
		<category><![CDATA[Website protection]]></category>
		<category><![CDATA[Website security]]></category>
		<category><![CDATA[Website updates]]></category>
		<category><![CDATA[Website vulnerabilities]]></category>
		<category><![CDATA[WordPress database]]></category>
		<category><![CDATA[WordPress security]]></category>
		<guid isPermaLink="false">https://tarheel.media/?p=3160</guid>

					<description><![CDATA[<p>The security firm, Cyllective, identified around 5,000 plugins on WordPress.org that contained various security exploits such as SQL Injections. The Penetration Testing Team lead, Dave Miller said what started as a random experiment turned into a treasure trove for hackers. Once they started the experiment, they were quickly surprised at how relaxed the security was  [...]</p>
<p>The post <a href="https://tarheel.media/security-bulletin/2023/05/17/outdated-wordpress-plugins-make-60000-websites-vulnerable/?pk_campaign=feed&#038;pk_kwd=outdated-wordpress-plugins-make-60000-websites-vulnerable">Outdated WordPress Plugins make 60,000 Websites Vulnerable</a> appeared first on <a href="https://tarheel.media">Tarheel Media</a>.</p>
]]></description>
										<content:encoded><![CDATA[<p>The security firm, Cyllective, identified around 5,000 plugins on WordPress.org that contained various security exploits such as SQL Injections. The Penetration Testing Team lead, Dave Miller said what started as a random experiment turned into a treasure trove for hackers. Once they started the experiment, they were quickly surprised at how relaxed the security was on WordPress.org&#8217;s repository in allowing old and exploitable plugins to remain and be installed.</p>
<p>If that wasn&#8217;t bad enough, Dave&#8217;s team came across remote code execution vulnerabilities or RCE&#8217;s. RCE&#8217;s are usually where bad code allows an attacker to gain administrative or super-user privileges and entirely take over a website or the entire information system.</p>
<p>Dave&#8217;s team, however, focused in on the SQL injections &#8211; a way of appending your own SQL query from code that does not escape its <span style="color: #008080;">$_POST</span> variables which is the variable where the stuff you submit to a website is stored. After just 3 months of research, Dave&#8217;s team found a staggering 35 plugins that had already been exploited by unauthorized users or hackers. While 35 sounds like a low number, those 35 plugins were in operation and were exploited on over 60,500 WordPress websites.</p>
<p>&#8220;Although the vast majority of the vulnerabilities I reported were unauthenticated SQL injection vulnerabilities, which would have enabled an attacker to dump the entire WordPress database contents, these were not the most devastating ones,” Dave said.</p>
<p>“The sitemap-by-click5 plugin suffered from an unauthenticated arbitrary options update flaw, which would have allowed an attacker to maliciously enable the registration functionality and set the default user role to that of an administrator.&#8221;</p>
<p>Dave explained that this would allow an attacker to create their own administrator account and entirely take over the WordPress website. Dave went on to say that he hopes this research forwards the ability to quickly identify security exploits in the future and minimize website intrusions.</p>
<p>After dealing with these WordPress Plugins and WordPress.org a pretty heavy blow, Dave did applaud the WordPress team for how well the disclosure process went in allowing Dave&#8217;s team to reach out and get these updates out there to these vulnerable websites that desperately needed it.</p>
<img decoding="async" src="https://stats.tarheel.media/piwik.php?idsite=1&amp;rec=1&amp;url=https%3A%2F%2Ftarheel.media%2Fsecurity-bulletin%2F2023%2F05%2F17%2Foutdated-wordpress-plugins-make-60000-websites-vulnerable%2F%3Fpk_campaign%3Dfeed%26pk_kwd%3Doutdated-wordpress-plugins-make-60000-websites-vulnerable&amp;action_name=Outdated%20WordPress%20Plugins%20make%2060%2C000%20Websites%20Vulnerable&amp;urlref=https%3A%2F%2Ftarheel.media%2Ffeed%2F" style="border:0;width:0;height:0" width="0" height="0" alt="" /><p>The post <a href="https://tarheel.media/security-bulletin/2023/05/17/outdated-wordpress-plugins-make-60000-websites-vulnerable/?pk_campaign=feed&#038;pk_kwd=outdated-wordpress-plugins-make-60000-websites-vulnerable">Outdated WordPress Plugins make 60,000 Websites Vulnerable</a> appeared first on <a href="https://tarheel.media">Tarheel Media</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
