<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[ShinyHunters hacked Clop leak site using Grav CMS path traversal flaw]]></title><description><![CDATA[<p dir="auto">The <strong>Clop</strong> ransomware gang has relocated its data leak site to a new <strong>Tor</strong> address after confirming that its previous server was compromised and defaced. The intrusion was carried out through an unpatched flaw in <strong>Grav CMS</strong>, which <strong>BleepingComputer</strong> has learned is an unauthenticated path traversal vulnerability.</p>
<p dir="auto">According to the reporting, the <strong>ShinyHunters</strong> group was behind the hack of the Clop leak site. The defacement prompted Clop to move its operations to a fresh Tor hidden service address, indicating the gang treated the compromise as serious enough to abandon the original infrastructure rather than simply restore it.</p>
<p dir="auto">Key points from the incident:</p>
<ul>
<li>The vulnerable software is <strong>Grav CMS</strong>, and the flaw is an <strong>unauthenticated path traversal</strong> issue.</li>
<li>The Clop leak site was both compromised and defaced before being moved.</li>
<li><strong>ShinyHunters</strong> has been credited with carrying out the attack.</li>
<li>Clop has since shifted its leak site to a <strong>new Tor address</strong>.</li>
</ul>
<p dir="auto">For defenders, this incident is a reminder that extortion groups are not immune to the same classes of bugs they exploit in others. An unauthenticated path traversal in a content management system can expose or allow manipulation of files on an internet-facing server, which is exactly the kind of exposure that can lead to a site being taken over or defaced.</p>
<p dir="auto">There is no specific CVE identifier or patch reference provided in the source report, so administrators running <strong>Grav CMS</strong> should monitor the project's official channels for updates rather than relying on a specific advisory number here.</p>
<p dir="auto">Source: <a href="https://www.bleepingcomputer.com/news/security/shinyhunters-hacked-clop-leak-site-using-grav-cms-path-traversal-flaw" target="_blank" rel="noopener noreferrer nofollow ugc">Unknown</a></p>
<p dir="auto">If your organization runs Grav CMS, have you checked whether it is fully patched and whether any instances are exposed directly to the internet?</p>
]]></description><link>https://xploitlk.com/topic/467/shinyhunters-hacked-clop-leak-site-using-grav-cms-path-traversal-flaw</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 08:16:03 GMT</lastBuildDate><atom:link href="https://xploitlk.com/topic/467.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 26 Sep 2026 00:30:23 GMT</pubDate><ttl>60</ttl></channel></rss>