<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-22T01:11:28.048424+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2020-29849</id>
    <title>cnvd-2020-29849</title>
    <updated>2026-10-22T01:11:28.098714+00:00</updated>
    <content>cnvd-2020-29849</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2020-29849"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-66791</id>
    <title>EUVD-2026-66791</title>
    <updated>2026-10-22T01:11:28.099159+00:00</updated>
    <content>EUVD-2026-66791</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-66791"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2018-14028</id>
    <title>fkie_cve-2018-14028</title>
    <updated>2026-10-22T01:11:28.099202+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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's wp-content/plugins directory permissions were set up to block all new plugins.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2018-14028"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fm2w-6w3p-hhx6</id>
    <title>GHSA-fm2w-6w3p-hhx6</title>
    <updated>2026-10-22T01:11:28.099291+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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's wp-content/plugins directory permissions were set up to block all new plugins.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fm2w-6w3p-hhx6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2018-14028</id>
    <title>gsd-2018-14028</title>
    <updated>2026-10-22T01:11:28.099327+00:00</updated>
    <content>gsd-2018-14028</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2018-14028"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-14028</id>
    <title>UBUNTU-CVE-2018-14028</title>
    <updated>2026-10-22T01:11:28.099351+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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's wp-content/plugins directory permissions were set up to block all new plugins.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2018-14028"/>
  </entry>
</feed>
