<?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>The Magento Expert</title>
	<atom:link href="https://www.the-mage-expert.com/tag/php/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.the-mage-expert.com</link>
	<description>Your Magento Commerce Expert</description>
	<lastBuildDate>Wed, 18 Nov 2026 21:23:52 +0000</lastBuildDate>
	<language>de-DE</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.8.6</generator>
	<item>
		<title>Critical PHP Vulnerabilities CVE-2026-109618 and CVE-2026-109619: Securing Magento Stores Running PHP Below 8</title>
		<link>https://www.the-mage-expert.com/3250/critical-php-vulnerabilities-cve-2026-109618-and-cve-2026-109619-securing-magento-stores-running-php-below-8/</link>
		<comments>https://www.the-mage-expert.com/3250/critical-php-vulnerabilities-cve-2026-109618-and-cve-2026-109619-securing-magento-stores-running-php-below-8/#comments</comments>
		<pubDate>Wed, 21 Oct 2026 19:35:14 +0000</pubDate>
		<dc:creator><![CDATA[Mex]]></dc:creator>
				<category><![CDATA[Magento Solutions]]></category>
		<category><![CDATA[magent]]></category>
		<category><![CDATA[Magento]]></category>
		<category><![CDATA[Magento 2]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">https://www.the-mage-expert.com/?p=3250</guid>
		<description><![CDATA[On October 21, 2026, two critical PHP vulnerabilities were disclosed. This is particularly troublesome for operators of older Magento stores still running PHP 5.6, PHP 7.4 or another unsupported PHP version. A simple PHP upgrade is often impossible without updating&#8230;]]></description>
				<content:encoded><![CDATA[<p>On October 21, 2026, two critical PHP vulnerabilities were disclosed. This is particularly troublesome for operators of older Magento stores still running PHP 5.6, PHP 7.4 or another unsupported PHP version. A simple PHP upgrade is often impossible without updating Magento and numerous extensions at the same time.</p>
<p>The vulnerabilities <strong>CVE-2026-109618</strong> and <strong>CVE-2026-109619</strong> may, under certain conditions, allow attackers to execute code on the server, potentially without being logged in first. Both were rated 9.2 in severity.</p>
<p><strong>Why older Magento stores are especially affected</strong></p>
<p>Many Magento 1 installations still rely on PHP 5.x or PHP 7.x. Older Magento 2 versions may also depend on specific PHP versions.</p>
<p>Switching to PHP 8.3 or 8.4 can therefore break a store. Outdated libraries, custom extensions and Magento core modifications can turn an upgrade into a substantial project.</p>
<p>The problem is: <strong>PHP 5.x and PHP 7.x no longer receive regular security updates.</strong> A store that ran perfectly yesterday may therefore face significant additional risk today.</p>
<p>Older PHP 8 versions may also be affected. A version number beginning with 8 does not, by itself, mean a system is secure.</p>
<p><strong>What can store owners do now?</strong></p>
<p>The good news is that reducing the immediate risk does not always require a complete Magento upgrade straight away.</p>
<p>Depending on your server configuration, consider the following:</p>
<ul>
<li><strong>Secure your web server:</strong> Block malicious requests as early as possible through Apache, nginx or an upstream firewall.</li>
<li><strong>Harden PHP configuration:</strong> Disable unnecessary PHP functions and restrict dangerous request processing at the server level.</li>
<li><strong>Protect the admin area:</strong> Add extra protection for Magento admin and reduce unnecessary public access.</li>
<li><strong>Check your hosting environment:</strong> Ask whether your provider supplies security fixes for the older PHP release you use.</li>
<li><strong>Review Magento extensions:</strong> Remove unused functionality and restrict potentially vulnerable interfaces.</li>
</ul>
<p><strong>Important:</strong> These measures do not replace a security patch for PHP itself. They can limit some attack vectors but cannot provide complete protection. In some cases, taking a vulnerable installation temporarily offline may be necessary.</p>
<p><strong>Why not simply upgrade PHP?</strong></p>
<p>With a current Magento 2 store, moving to a supported PHP version may be relatively straightforward if the installed extensions are compatible.</p>
<p>Magento 1 and older Magento 2 installations are different. Their dependencies must be reviewed first. Some extensions can be adapted; elsewhere, a more substantial modernization may be required.</p>
<p>A blanket PHP upgrade is therefore not a good idea. The store still needs to work properly after the security changes.</p>
<p><strong>I can help secure your Magento store</strong></p>
<p>Running Magento 1 or Magento 2 on PHP 5.6, 7.4 or another outdated PHP version and unsure how to respond to the latest security vulnerabilities?</p>
<p>Please <a href="https://www.the-mage-expert.com/contact/">contact me</a>.</p>
<p>I can assess your Magento installation, PHP environment and options for short-term mitigation. The first priority is understanding the real exposure and implementing sensible measures without unnecessarily disrupting a working store.</p>
<p>If a lasting upgrade is needed, we can plan the appropriate route, from adapting individual extensions to a full Magento upgrade.</p>
<p><strong>Further information</strong></p>
<p>Official details about the vulnerabilities, affected PHP versions and available patches can be found directly from <a href="https://www.php.net/archive/2026.php" target="_blank" rel="noopener">PHP development team</a>.</p>]]></content:encoded>
			<wfw:commentRss>https://www.the-mage-expert.com/3250/critical-php-vulnerabilities-cve-2026-109618-and-cve-2026-109619-securing-magento-stores-running-php-below-8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Fixing undefined SODIUM_CRYPTO_AEAD_CHACHA20POLY1305_IETF_NPUBBYTES constant</title>
		<link>https://www.the-mage-expert.com/2047/fixing-undefined-sodium-crypto-aead-chacha20poly1305-ietf-npubbytes-constant/</link>
		<comments>https://www.the-mage-expert.com/2047/fixing-undefined-sodium-crypto-aead-chacha20poly1305-ietf-npubbytes-constant/#comments</comments>
		<pubDate>Wed, 08 Feb 2023 09:21:51 +0000</pubDate>
		<dc:creator><![CDATA[Mex]]></dc:creator>
				<category><![CDATA[Magento Solutions]]></category>
		<category><![CDATA[Magento 2]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Sodium]]></category>

		<guid isPermaLink="false">https://www.the-mage-expert.com/?p=2047</guid>
		<description><![CDATA[If the message Undefined constant &#8220;Magento\Framework\Encryption\Adapter\SODIUM_CRYPTO_AEAD_CHACHA20POLY1305_IETF_NPUBBYTES appears in your Magento 2 store, the PHP sodium extension is almost certainly missing or disabled. Install or enable sodium and the error should be resolved.]]></description>
				<content:encoded><![CDATA[<p>If the message <strong>Undefined constant &#8220;Magento\Framework\Encryption\Adapter\SODIUM_CRYPTO_AEAD_CHACHA20POLY1305_IETF_NPUBBYTES</strong> appears in your Magento 2 store, the PHP sodium extension is almost certainly missing or disabled. Install or enable sodium and the error should be resolved.</p>]]></content:encoded>
			<wfw:commentRss>https://www.the-mage-expert.com/2047/fixing-undefined-sodium-crypto-aead-chacha20poly1305-ietf-npubbytes-constant/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento 1 and PHP 5.6 support</title>
		<link>https://www.the-mage-expert.com/1472/magento-1-and-php-5-6-support/</link>
		<comments>https://www.the-mage-expert.com/1472/magento-1-and-php-5-6-support/#comments</comments>
		<pubDate>Thu, 18 Oct 2018 09:30:27 +0000</pubDate>
		<dc:creator><![CDATA[Mex]]></dc:creator>
				<category><![CDATA[Magento Solutions]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHP 7]]></category>

		<guid isPermaLink="false">https://www.the-mage-expert.com/?p=1472</guid>
		<description><![CDATA[Support for PHP 5.6 ends at the end of 2018! Many hosting providers may therefore stop offering this PHP version. Act early and make your Magento 1 store ready for PHP 7. In many cases, the switch is manageable in&#8230;]]></description>
				<content:encoded><![CDATA[<p><strong>Support for PHP 5.6 ends at the end of 2018!</strong> Many hosting providers may therefore stop offering this PHP version. Act early and make your Magento 1 store ready for PHP 7.</p>
<p>In many cases, the switch is manageable in both time and cost. Read more about Magento 1 and PHP 7 in my article <a href="https://www.the-mage-expert.com/1450/magento-1-and-php-7/" target="_blank">Magento 1 and PHP 7</a>.</p>
<p>Would you like your store migrated to PHP 7? Please <a href="https://www.the-mage-expert.com/contact/">get in touch</a> and I will be happy to help. </p>]]></content:encoded>
			<wfw:commentRss>https://www.the-mage-expert.com/1472/magento-1-and-php-5-6-support/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Magento 1 and PHP 7</title>
		<link>https://www.the-mage-expert.com/1450/magento-1-and-php-7/</link>
		<comments>https://www.the-mage-expert.com/1450/magento-1-and-php-7/#comments</comments>
		<pubDate>Fri, 29 Jun 2018 08:36:25 +0000</pubDate>
		<dc:creator><![CDATA[Mex]]></dc:creator>
				<category><![CDATA[Magento Solutions]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[PHP 7]]></category>

		<guid isPermaLink="false">https://www.the-mage-expert.com/?p=1450</guid>
		<description><![CDATA[The benefits of PHP 7 are clear: it is faster and more secure than older versions, and offers developers new ways to write code and build features. Sooner or later, any Magento 1 store owner will reasonably ask whether the&#8230;]]></description>
				<content:encoded><![CDATA[<p>The benefits of PHP 7 are clear: it is faster and more secure than older versions, and offers developers new ways to write code and build features. Sooner or later, any Magento 1 store owner will reasonably ask whether the store can simply be switched to PHP 7 without preparation.</p>
<p><strong>Switching Magento 1 to PHP 7 can cause compatibility problems.</strong> These are often caused by third-party extensions, but they can usually be resolved. If you want to benefit from PHP 7, have your Magento store assessed before the switch. In many cases, the upgrade can then be completed with relatively little effort.</p>
<p><a href="https://www.the-mage-expert.com/contact/" target='_blank'>Get in touch</a> and I will be happy to advise you and carry out the migration.</p>]]></content:encoded>
			<wfw:commentRss>https://www.the-mage-expert.com/1450/magento-1-and-php-7/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Solving &#8220;Cannot send headers; headers already sent&#8221; problem</title>
		<link>https://www.the-mage-expert.com/709/magento-solving-cannot-send-headers-headers-already-sent-problem/</link>
		<comments>https://www.the-mage-expert.com/709/magento-solving-cannot-send-headers-headers-already-sent-problem/#comments</comments>
		<pubDate>Thu, 13 Nov 2014 09:20:35 +0000</pubDate>
		<dc:creator><![CDATA[Mex]]></dc:creator>
				<category><![CDATA[Magento Solutions]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">https://www.the-mage-expert.com/?p=709</guid>
		<description><![CDATA[Sometimes, when looking through your Magento log files, you might stumble upon the &#8220;Cannot send headers; headers already sent in &#8230;&#8221; message. One possible reason for that could be a space or a newline behind a closing PHP tag (?>).&#8230;]]></description>
				<content:encoded><![CDATA[<p>Sometimes, when looking through your Magento log files, you might stumble upon the &#8220;Cannot send headers; headers already sent in &#8230;&#8221; message. One possible reason for that could be a space or a newline behind a closing PHP tag (?>). To solve the problem, just open the file being mentioned in the log file and remove the space or newline.</p>]]></content:encoded>
			<wfw:commentRss>https://www.the-mage-expert.com/709/magento-solving-cannot-send-headers-headers-already-sent-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
