<?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://cve.radiocsirt.org</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, 19 Oct 2026 15:51:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-7547 — Woosa &lt;= 2.0.5 - Authenticated (Administrator+) Arbitrary File Read via 'log_file' Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-7547</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; teamwsa Woosa – Marktplaats for WooCommerce&lt;/p&gt;
&lt;p&gt;The Woosa – Marktplaats for WooCommerce plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in versions up to and including 2.0.4. This is due to insufficient path sanitization in the render_logs_ui() function, which accepts a base64-encoded file name from the &amp;#39;log_file&amp;#39; GET parameter and concatenates it directly with the plugin&amp;#39;s log directory path without validating that the resolved path remains within the intended directory. This makes it possible for authenticated attackers, with Administrator-level access, to read the contents of arbitrary files on the server, including wp-config.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; teamwsa Woosa – Marktplaats for WooCommerce&lt;/p&gt;
&lt;p&gt;The Woosa – Marktplaats for WooCommerce plugin for WordPress is vulnerable to Arbitrary File Read via Path Traversal in versions up to and including 2.0.4. This is due to insufficient path sanitization in the render_logs_ui() function, which accepts a base64-encoded file name from the &amp;#39;log_file&amp;#39; GET parameter and concatenates it directly with the plugin&amp;#39;s log directory path without validating that the resolved path remains within the intended directory. This makes it possible for authenticated attackers, with Administrator-level access, to read the contents of arbitrary files on the server, including wp-config.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-7547</guid>
    </item>
  </channel>
</rss>
