<?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>file upload - Matteo Cisilino</title>
	<atom:link href="https://www.cisilino.com/en/tag/file-upload/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:09 +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>Dangerous file uploads in WordPress: double extensions</title>
		<link>https://www.cisilino.com/en/2026/11/11/dangerous-file-uploads-wordpress/</link>
					<comments>https://www.cisilino.com/en/2026/11/11/dangerous-file-uploads-wordpress/#respond</comments>
		
		<dc:creator><![CDATA[matteocisilino]]></dc:creator>
		<pubDate>Wed, 11 Nov 2026 17:43:00 +0000</pubDate>
				<category><![CDATA[csdn]]></category>
		<category><![CDATA[double extension]]></category>
		<category><![CDATA[file upload]]></category>
		<category><![CDATA[hardening]]></category>
		<category><![CDATA[webshell]]></category>
		<category><![CDATA[WordPress malware]]></category>
		<guid isPermaLink="false">https://www.cisilino.com/?p=164</guid>

					<description><![CDATA[<p>Dangerous uploads in WordPress don't only come through the media library. How to spot double extensions like image.php.jpg and reject them.</p>
<p>The post <a href="https://www.cisilino.com/en/2026/11/11/dangerous-file-uploads-wordpress/">Dangerous file uploads in WordPress: double extensions</a> first appeared on <a href="https://www.cisilino.com/en/">Matteo Cisilino</a>.</p>]]></description>
										<content:encoded><![CDATA[<p>People assume files enter WordPress through the media library. In reality <strong>dangerous uploads in WordPress</strong> often arrive some other way. Think of a plugin form, an <code>admin-ajax</code> endpoint, an upload inside the theme. These are routes that ordinary checks don&#8217;t look at.</p>
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" src="https://www.cisilino.com/wp-content/uploads/2026/10/dangerous-file-upload-wordpress.webp" alt="Dangerous uploads in WordPress: two overlapping sheets, the front one with a blue circle containing a cross" width="1200" height="630"/></figure>
<h2>What the plugin records about dangerous uploads in WordPress</h2>
<p>Every file that enters the site is recorded, even if it doesn&#8217;t go through the media library, because dangerous uploads in WordPress rarely do. Executable extensions are flagged, including double extensions such as <code>immagine.php.jpg</code>. It also recognises <code>.user.ini</code>, which on PHP-FPM is worth the same as a <code>.htaccess</code>. It also recognises SVG files and names built with null bytes or trailing spaces to disguise the extension.</p>
<h2>Record or reject</h2>
<p>There is also an option to reject dangerous uploads in WordPress, off by default. Some plugins legitimately upload archives or unusual files. The advice is to start with monitoring only, watch the log for a few weeks and then decide.</p>
<h2>Checking that the block really works</h2>
<p>In the <em>Test</em> tab there is a check that the PHP execution block in <code>uploads</code> works on your site, instead of trusting only the saved setting. On some hosts the <code>.htaccess</code> rules are ignored: better to find out yourself than during an incident caused by dangerous uploads in WordPress. OWASP describes this class of risk as <a href="https://owasp.org/www-community/vulnerabilities/Unrestricted_File_Upload" target="_blank" rel="noopener">unrestricted file upload</a>. It is a good read on why checking only the extension is not enough.</p>
<h2>An example of dangerous uploads in WordPress</h2>
<p>A job application form that accepts CVs and checks extensions badly is a classic route for dangerous uploads in WordPress. A bot uploads <code>cv.php.pdf</code>. The log shows it with the executable extension warning. With the PHP block in <code>uploads</code> switched on, the file cannot be executed even though it got in.</p>
<h2>Frequently asked questions</h2>
<h3>What is a double extension in uploaded files?</h3>
<p>A name like image.php.jpg, meant to look like an image but which in some configurations can be executed as PHP. The plugin flags it.</p>
<h3>Does the plugin block dangerous uploads in WordPress?</h3>
<p>It can reject them, but the option is off by default because some plugins upload unusual files legitimately. By default it records and flags them.</p>
<h3>How do I check that the PHP block in uploads works?</h3>
<p>With the test in the plugin&#8217;s Test tab, which tries the block on the live site.</p>
<h2>Read more</h2>
<ul>
<li><a href="https://www.cisilino.com/en/?p=93">WordPress hardening with .htaccess: what to switch on</a></li>
<li><a href="https://www.cisilino.com/en/?p=89">WordPress webshell: how to find it with file integrity checks</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/dangerous-file-uploads-wordpress/">Dangerous file uploads in WordPress: double extensions</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/dangerous-file-uploads-wordpress/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
