

<?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"

			>

	<channel>
		<title>LexiConn News  &#187;  Topic: Magento security patch SUPEE-7405 &#8211; All eligible hosted stores patched</title>
		<atom:link href="https://support.lexiconn.com/news/forums/topic/magento-security-patch-supee-7405-all-eligible-hosted-stores-patched/feed" rel="self" type="application/rss+xml" />
		<link>https://support.lexiconn.com/news/forums/topic/magento-security-patch-supee-7405-all-eligible-hosted-stores-patched/feed</link>
		<description></description>
		<pubDate>Sun, 05 Apr 2026 12:08:29 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.5.3-5249</generator>
		<language>en-US</language>

		
														
					
				<item>
					<guid>https://support.lexiconn.com/news/forums/topic/magento-security-patch-supee-7405-all-eligible-hosted-stores-patched/#post-49217</guid>
					<title><![CDATA[Magento security patch SUPEE-7405 &#8211; All eligible hosted stores patched]]></title>
					<link>https://support.lexiconn.com/news/forums/topic/magento-security-patch-supee-7405-all-eligible-hosted-stores-patched/#post-49217</link>
					<pubDate>Sat, 23 Jan 2016 22:49:17 +0000</pubDate>
					<dc:creator>lexiconn</dc:creator>

					<description>
						<![CDATA[
						<p>Magento has released a <strong><span style="text-decoration: underline;"><a href="https://magento.com/security/patches/supee-7405" target="_blank" rel="nofollow">new security patch SUPEE-7405</a></span></strong>. It addresses a number of vulnerabilities. A few of these vulnerabilities allow a <strong><span style="text-decoration: underline;"><a href="https://blog.sucuri.net/2016/01/security-advisory-stored-xss-in-magento.html" target="_blank" rel="nofollow">remote user to create a malicious customer email address</a></span></strong> that can cause a store to be compromised. It is a highly recommended patch by Magento.</p>
<p>Any hosted Magento store with us that already had the previous SUPEE-6788 patch has been automatically patched with this latest release. For those stores that do not have the SUPEE-6788 patch already applied, we will be contacting those stores about what is required to apply the previous patch (the 6788 patch is not a seamless patch, and can break functionality in a Magento store).</p>
<p>You can view the contents of the file &#8220;app/etc/applied.patches.list&#8221; in your store (via FTP or ssh) to see which patches have been applied. If you have any questions, please contact us.</p>
<p>As is our policy, once a security patch is released by Magento, we thoroughly test it (this latest one has a few &#8220;gotchas&#8221; with permissions that we have addressed in our hosting environment), and then deploy it on any hosted Magento store where it can be applied seamlessly. For those stores where a problem may occur, we contact the affected client with options and recommendations for how the patch may be applied.</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

