<?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-24T02:45:12.264852+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/euvd-2026-172604</id>
    <title>EUVD-2026-172604</title>
    <updated>2026-10-24T02:45:12.268010+00:00</updated>
    <content>EUVD-2026-172604</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-172604"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2011-4451</id>
    <title>fkie_cve-2011-4451</title>
    <updated>2026-10-24T02:45:12.268056+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>libs/Wakka.class.php in WikkaWiki 1.3.1 and 1.3.2, when the spam_logging option is enabled, allows remote attackers to write arbitrary PHP code to the spamlog_path file via the User-Agent HTTP header in an addcomment request.  NOTE: the vendor disputes this issue because the rendering of the spamlog_path file never uses the PHP interpreter</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2011-4451"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-65vv-mx5f-jggq</id>
    <title>GHSA-65vv-mx5f-jggq</title>
    <updated>2026-10-24T02:45:12.268104+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>** DISPUTED ** libs/Wakka.class.php in WikkaWiki 1.3.1 and 1.3.2, when the spam_logging option is enabled, allows remote attackers to write arbitrary PHP code to the spamlog_path file via the User-Agent HTTP header in an addcomment request.  NOTE: the vendor disputes this issue because the rendering of the spamlog_path file never uses the PHP interpreter.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-65vv-mx5f-jggq"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2011-4451</id>
    <title>gsd-2011-4451</title>
    <updated>2026-10-24T02:45:12.268132+00:00</updated>
    <content>gsd-2011-4451</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2011-4451"/>
  </entry>
</feed>
