<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 16:23:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-5114 — SpeedyCache &lt;= 1.3.8 - Authenticated (Administrator+) Arbitrary File Read</title>
      <link>https://db.gcve.eu/vuln/cve-2026-5114</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; softaculous SpeedyCache – Cache, Optimization, Performance&lt;/p&gt;
&lt;p&gt;The SpeedyCache plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in all versions up to, and including, 1.3.8. This is due to a mismatch between CSS URL validation (which allows query strings like `.css?...`) and path resolution (which strips query strings), combined with no validation that the resolved file is actually a CSS file. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files from the server (including `wp-config.php` and `/etc/passwd`) by injecting crafted `&amp;lt;link&amp;gt;` tags into page content, with the file contents written to publicly accessible cache files.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; softaculous SpeedyCache – Cache, Optimization, Performance&lt;/p&gt;
&lt;p&gt;The SpeedyCache plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in all versions up to, and including, 1.3.8. This is due to a mismatch between CSS URL validation (which allows query strings like `.css?...`) and path resolution (which strips query strings), combined with no validation that the resolved file is actually a CSS file. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files from the server (including `wp-config.php` and `/etc/passwd`) by injecting crafted `&amp;lt;link&amp;gt;` tags into page content, with the file contents written to publicly accessible cache files.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-5114</guid>
    </item>
  </channel>
</rss>
