<?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>Tue, 10 Nov 2026 04:04:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-120548 — YML for Yandex Market &lt;= 5.10.0 - Unauthenticated Sensitive Information Exposure through Log File via 'y4ym_check_actio…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-120548</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; icopydoc YML for Yandex Market&lt;/p&gt;
&lt;p&gt;The YML for Yandex Market plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.10.0 via the &amp;#39;y4ym_check_action&amp;#39; parameter. This makes it possible for unauthenticated attackers to extract the merchant&amp;#39;s plaintext Yandex Market API key written to the publicly accessible log file at wp-content/uploads/y4ym/yml-for-yandex-market.log, granting full control over the merchant&amp;#39;s marketplace catalogue, prices, and stock. Exploitation requires that the targeted feed has a stored Yandex Market API key and that the y4ym_keeplogs option is enabled — both conditions that represent normal, documented plugin usage actively encouraged by the plugin&amp;#39;s own support and feedback workflow.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; icopydoc YML for Yandex Market&lt;/p&gt;
&lt;p&gt;The YML for Yandex Market plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.10.0 via the &amp;#39;y4ym_check_action&amp;#39; parameter. This makes it possible for unauthenticated attackers to extract the merchant&amp;#39;s plaintext Yandex Market API key written to the publicly accessible log file at wp-content/uploads/y4ym/yml-for-yandex-market.log, granting full control over the merchant&amp;#39;s marketplace catalogue, prices, and stock. Exploitation requires that the targeted feed has a stored Yandex Market API key and that the y4ym_keeplogs option is enabled — both conditions that represent normal, documented plugin usage actively encouraged by the plugin&amp;#39;s own support and feedback workflow.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-120548</guid>
    </item>
  </channel>
</rss>
