<?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>Sat, 10 Oct 2026 06:29:57 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-18536</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-18536</link>
      <description>cnvd-2020-18536</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-18536</guid>
    </item>
    <item>
      <title>EUVD-2026-39695</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-39695</link>
      <description>EUVD-2026-39695</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-39695</guid>
    </item>
    <item>
      <title>fkie_cve-2020-10212</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-10212</link>
      <description>&lt;p&gt;upload.php in Responsive FileManager 9.13.4 and 9.14.0 allows SSRF via the url parameter because file-extension blocking is mishandled and because it is possible for a DNS hostname to resolve to an internal IP address. For example, an SSRF attempt may succeed if a .ico filename is added to the PATH_INFO. Also, an attacker could create a DNS hostname that resolves to the 0.0.0.0 IP address for DNS pinning. NOTE: this issue exists because of an incomplete fix for CVE-2018-14728.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;upload.php in Responsive FileManager 9.13.4 and 9.14.0 allows SSRF via the url parameter because file-extension blocking is mishandled and because it is possible for a DNS hostname to resolve to an internal IP address. For example, an SSRF attempt may succeed if a .ico filename is added to the PATH_INFO. Also, an attacker could create a DNS hostname that resolves to the 0.0.0.0 IP address for DNS pinning. NOTE: this issue exists because of an incomplete fix for CVE-2018-14728.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-10212</guid>
    </item>
    <item>
      <title>GHSA-66f3-j5p3-p6pc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-66f3-j5p3-p6pc</link>
      <description>&lt;p&gt;upload.php in Responsive FileManager 9.13.4 and 9.14.0 allows SSRF via the url parameter because file-extension blocking is mishandled and because it is possible for a DNS hostname to resolve to an internal IP address. For example, an SSRF attempt may succeed if a .ico filename is added to the PATH_INFO. Also, an attacker could create a DNS hostname that resolves to the 0.0.0.0 IP address for DNS pinning. NOTE: this issue exists because of an incomplete fix for CVE-2018-14728.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;upload.php in Responsive FileManager 9.13.4 and 9.14.0 allows SSRF via the url parameter because file-extension blocking is mishandled and because it is possible for a DNS hostname to resolve to an internal IP address. For example, an SSRF attempt may succeed if a .ico filename is added to the PATH_INFO. Also, an attacker could create a DNS hostname that resolves to the 0.0.0.0 IP address for DNS pinning. NOTE: this issue exists because of an incomplete fix for CVE-2018-14728.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-66f3-j5p3-p6pc</guid>
    </item>
    <item>
      <title>gsd-2020-10212</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-10212</link>
      <description>gsd-2020-10212</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-10212</guid>
    </item>
  </channel>
</rss>
