<?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>compromised account - Matteo Cisilino</title>
	<atom:link href="https://www.cisilino.com/en/tag/compromised-account/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.cisilino.com/en/</link>
	<description>Guide su WordPress, server e sicurezza</description>
	<lastBuildDate>Wed, 11 Nov 2026 17:52:52 +0000</lastBuildDate>
	<language>en-GB</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>Compromised WordPress account: suspend users who publish too much</title>
		<link>https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/</link>
					<comments>https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 17:46:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[compromised account]]></category>
		<category><![CDATA[rate limiting]]></category>
		<category><![CDATA[spam]]></category>
		<category><![CDATA[WordPress users]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=167</guid>

					<description><![CDATA[<p>A compromised WordPress account can publish hundreds of spam pages in minutes. The author limit suspends the user before the damage is done.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/">Compromised WordPress account: suspend users who publish too much</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>It happens more than you would think. A <strong>compromised WordPress account</strong>, perhaps with author permissions, publishes dozens or hundreds of spam pages within minutes. By the time you notice, search engines have already seen something.</p>
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/compromised-wordpress-account-suspension.webp" alt="Compromised WordPress account: a user icon inside a circle, with a yellow pause symbol at the bottom right" width="1200" height="630"/></figure>
<h2>What the author limit does to a compromised WordPress account</h2>
<p>It counts how many posts or pages a user creates or publishes within a time window. If they go over the threshold, as happens with a compromised WordPress account, they are <strong>suspended</strong> for a length of time you choose. They can no longer create or publish, but their role stays the same. The main administrator can receive an email with the recent content to check. The suspension does not change or delete anything.</p>
<h2>The default, and why it changed</h2>
<p>As of version 1.0.13 the default limit is 150 items in 5 minutes. Before it was 3, and it also suspended an administrator who was simply importing or duplicating pages. The new value copes with real heavy use and still stops a compromised WordPress account publishing hundreds in one go. Anyone who had already customised the value is left untouched.</p>
<h2>What counts and what doesn&#8217;t</h2>
<p>Only posts and pages count towards flagging a compromised WordPress account. Plugin installs and updates, logins, autosaves, revisions, trash, media and other content types do not. Neither does anything that happens in a temporary installation with a different table prefix. Plugin Check creates one with a sample post and page, and in the past it suspended whoever was using it.</p>
<h2>What a suspended user sees</h2>
<p>A notice in the dashboard with the reason and the end date. Administrators see the list of suspended users with a link to revoke. Revoking can also be done from the <em>Rate limiting</em> tab, before the suspension expires.</p>
<p>The limit is a brake and a doorbell, not proof: the email is there to help you decide quickly whether it is a compromised WordPress account or very heavy legitimate use. If it is a real compromise, the official guide <a href="https://wordpress.org/documentation/article/faq-my-site-was-hacked/" target="_blank" rel="noopener">My site was hacked</a> is a good starting point for the clean-up.</p>
<h2>Frequently asked questions</h2>
<h3>How do you stop a compromised WordPress account that is publishing spam?</h3>
<p>By limiting how much content it can create within a time window. The plugin suspends the user who goes over the threshold, without changing their role or deleting their content.</p>
<h3>What is the default threshold?</h3>
<p>From version 1.0.13 it is 150 items in 5 minutes. Threshold, window and suspension length are all configurable.</p>
<h3>Can an administrator be suspended by mistake?</h3>
<p>With the default value it is unlikely, even when importing many pages. A suspension can be revoked at any time from the Rate limiting tab.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/en/?p=99">Comment spam and Contact Form 7: limiting visitors</a></li>
<li><a href="https://www.cisilino.com/en/?p=101">Secure WordPress user registration: roles and email</a></li>
<li><a href="https://www.cisilino.com/en/2026/10/29/cisilino-site-defense-network-security-plugin/">Cisilino Site Defense Network: the WordPress security plugin</a></li>
</ul><p>The post <a href="https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/">Compromised WordPress account: suspend users who publish too much</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://www.cisilino.com/en/2026/11/11/compromised-wordpress-account/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
