<?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>WordPress users - Matteo Cisilino</title>
	<atom:link href="https://www.cisilino.com/en/tag/wordpress-users/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:53:14 +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>Secure WordPress user registration: roles and email</title>
		<link>https://www.cisilino.com/en/2026/11/11/secure-wordpress-user-registration/</link>
					<comments>https://www.cisilino.com/en/2026/11/11/secure-wordpress-user-registration/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 17:48:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[user registration]]></category>
		<category><![CDATA[WordPress roles]]></category>
		<category><![CDATA[WordPress security]]></category>
		<category><![CDATA[WordPress users]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=169</guid>

					<description><![CDATA[<p>Secure WordPress user registration starts with roles: three policies to decide who can become what, whichever door the user comes in through.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/11/secure-wordpress-user-registration/">Secure WordPress user registration: roles and email</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>Many attacks don&#8217;t force anything: they exploit open registration or a plugin that creates users. They give themselves a high role. A <strong>secure WordPress user registration</strong> starts by deciding who can become what. The plugin&#8217;s <em>User registration</em> section does exactly that.</p>
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/secure-user-registration-wordpress.webp" alt="WordPress user registration: a user icon next to three lines ending in circles of increasing size" width="1200" height="630"/></figure>
<h2>Three WordPress user registration policies</h2>
<p>WordPress user registration here follows one of three policies:</p>
<ol>
<li>No restriction.</li>
<li>Low-privilege roles only: never administrator, editor, author or shop_manager.</li>
<li>Registration switched off entirely.</li>
</ol>
<p>The second one is on by default. As soon as it is installed, the plugin already prevents the creation of high-privilege accounts, even if the configuration is wrong. The official documentation on <a href="https://wordpress.org/documentation/article/roles-and-capabilities/" target="_blank" rel="noopener">roles and capabilities</a> explains what each default role can do.</p>
<h2>Whichever door they come in through</h2>
<p>The WordPress user registration policy uses WordPress&#8217;s central filter for user creation. So it covers wp-admin, the REST API, XML-RPC, WP-CLI and direct calls from third-party plugins or themes. As a safety net, an account created while the policy was active with permissions it shouldn&#8217;t have loses them immediately. That holds whichever way it came in.</p>
<h2>Always a valid email at WordPress user registration</h2>
<p>A separate switch for WordPress user registration prevents users being created without a valid email address, from any route. Accounts without an email are hard to contact and to recognise: with email required, every user can be traced.</p>
<h2>A typical case</h2>
<p>An online shop with a vulnerable WordPress user registration plugin: the attacker tries to register asking for the administrator role. With the low-privilege roles policy the request does not produce an administrator. Another scenario stays out of reach: a vulnerability that edits the database directly bypasses the policy. It doesn&#8217;t go through user creation.</p>
<p>Creation, deletion and role changes end up in the activity log, which is useful for reconstructing what happened.</p>
<h2>Frequently asked questions</h2>
<h3>How do I stop someone registering as an administrator?</h3>
<p>With the low-privilege roles policy, on by default: administrator, editor, author and shop_manager cannot be created.</p>
<h3>Does it also apply to creations by plugins or WP-CLI?</h3>
<p>Yes, it covers wp-admin, the REST API, XML-RPC, WP-CLI and direct calls from plugins and themes.</p>
<h3>Is email mandatory for WordPress user registration?</h3>
<p>With the dedicated switch on, yes: no user can be created without a valid email address.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/en/?p=87">WordPress activity log: who changed what</a></li>
<li><a href="https://www.cisilino.com/en/?p=97">Compromised WordPress account: suspend users who publish too much</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/secure-wordpress-user-registration/">Secure WordPress user registration: roles and email</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/secure-wordpress-user-registration/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<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 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>
		<item>
		<title>WordPress activity log: who changed what</title>
		<link>https://www.cisilino.com/en/2026/11/09/wordpress-activity-log/</link>
					<comments>https://www.cisilino.com/en/2026/11/09/wordpress-activity-log/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Mon, 09 Nov 2026 08:00:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[activity log]]></category>
		<category><![CDATA[audit log]]></category>
		<category><![CDATA[change tracking]]></category>
		<category><![CDATA[WordPress users]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=162</guid>

					<description><![CDATA[<p>A WordPress activity log that tracks logins, users, content and plugins, with the before and after of settings, without storing secrets.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/09/wordpress-activity-log/">WordPress activity log: who changed what</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>The customer calls: &#8220;the site has changed and I haven&#8217;t touched anything&#8221;. Without a <strong>WordPress activity log</strong> the answer is a guess. With the plugin&#8217;s <em>Activity log</em> tab it is one line with a date, a user and an action.</p>
<figure class="wp-block-image size-large"><img decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/activity-log-wordpress.webp" alt="WordPress activity log: a list of five rows joined by a vertical line, with one pink row highlighted" width="1200" height="630"/></figure>
<h2>What goes into the WordPress activity log</h2>
<p>Logins and logouts, failed logins, users created, deleted or given a different role, content published or deleted, comments, media, plugins and themes activated or updated, core updates, important settings, menus, widgets, file edits from the admin area, and exports. Each group in the WordPress activity log can be switched on and off independently.</p>
<h2>Before and after, but no secrets</h2>
<p>When a setting changes, in the plugin or in another plugin that uses the WordPress Settings API, the WordPress activity log shows the old value and the new one, only for the fields that really changed. If the option name suggests a secret (key, token, password, licence) the value is never stored. You know it changed, not what it became. A log that leaves the site must not carry along the very things it is meant to protect.</p>
<h2>First on the site, then to the panel</h2>
<p>Every event in the WordPress activity log is written immediately to the local database. If you have connected a panel, it is sent at the end of the request, after answering the visitor. The site never waits for the panel. If the panel is down the event stays in the queue and is retried. The daily clean-up only deletes events that have already been confirmed.</p>
<h2>How much space it takes</h2>
<p>The local log has a row cap, 500 by default. It also grows with anonymous requests such as failed logins and comments. Retention on the panel is a separate setting: shortening the local one does not touch the history already delivered. To decide what is worth logging, the <a href="https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html" target="_blank" rel="noopener">OWASP Logging Cheat Sheet</a> is a solid reference.</p>
<p>Touching the WordPress activity log leaves a trace too. Emptying it, deactivating or uninstalling the plugin are logged events. The plugin also tries to deliver the last entry to the panel before removing the data. That way you can tell a plugin removed on purpose from a site that has gone silent. The log never contains the text of a post, a comment or a file.</p>
<h2>Frequently asked questions</h2>
<h3>Does the WordPress activity log store passwords or content?</h3>
<p>No. It never records passwords or the content of posts, comments or files.</p>
<h3>What happens if the panel cannot be reached?</h3>
<p>Events stay in the queue on the site and are retried. The automatic clean-up only deletes the ones the panel has confirmed.</p>
<h3>Does emptying the local log also delete the history on the panel?</h3>
<p>No. The plugin does not send any delete command to the panel.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/?p=89">WordPress webshell: how to find it with file integrity checks</a></li>
<li><a href="https://www.cisilino.com/?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/09/wordpress-activity-log/">WordPress activity log: who changed what</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/09/wordpress-activity-log/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
