<?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>Thu, 22 Oct 2026 01:11:27 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-29849</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-29849</link>
      <description>cnvd-2020-29849</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-29849</guid>
    </item>
    <item>
      <title>EUVD-2026-66791</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-66791</link>
      <description>EUVD-2026-66791</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-66791</guid>
    </item>
    <item>
      <title>fkie_cve-2018-14028</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2018-14028</link>
      <description>&lt;p&gt;In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine&amp;#39;s wp-content/plugins directory permissions were set up to block all new plugins.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine&amp;#39;s wp-content/plugins directory permissions were set up to block all new plugins.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2018-14028</guid>
    </item>
    <item>
      <title>GHSA-fm2w-6w3p-hhx6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fm2w-6w3p-hhx6</link>
      <description>&lt;p&gt;In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine&amp;#39;s wp-content/plugins directory permissions were set up to block all new plugins.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine&amp;#39;s wp-content/plugins directory permissions were set up to block all new plugins.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fm2w-6w3p-hhx6</guid>
    </item>
    <item>
      <title>gsd-2018-14028</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2018-14028</link>
      <description>gsd-2018-14028</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2018-14028</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2018-14028</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-14028</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: wordpress, Ubuntu:18.04:LTS: wordpress, Ubuntu:20.04:LTS: wordpress, Ubuntu:22.04:LTS: wordpress, Ubuntu:24.04:LTS: wordpress, Ubuntu:25.10: wordpress, Ubuntu:26.10: wordpress, Ubuntu:26.04:LTS: wordpress&lt;/p&gt;
&lt;p&gt;In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine&amp;#39;s wp-content/plugins directory permissions were set up to block all new plugins.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: wordpress, Ubuntu:18.04:LTS: wordpress, Ubuntu:20.04:LTS: wordpress, Ubuntu:22.04:LTS: wordpress, Ubuntu:24.04:LTS: wordpress, Ubuntu:25.10: wordpress, Ubuntu:26.10: wordpress, Ubuntu:26.04:LTS: wordpress&lt;/p&gt;
&lt;p&gt;In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine&amp;#39;s wp-content/plugins directory permissions were set up to block all new plugins.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-14028</guid>
    </item>
  </channel>
</rss>
