<?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>Wed, 07 Oct 2026 16:28:28 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-282738</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-282738</link>
      <description>EUVD-2026-282738</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-282738</guid>
    </item>
    <item>
      <title>fkie_cve-2026-1866</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-1866</link>
      <description>&lt;p&gt;The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin&amp;#39;s sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the &amp;#39;name_directory_name&amp;#39; and &amp;#39;name_directory_description&amp;#39; parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin&amp;#39;s sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the &amp;#39;name_directory_name&amp;#39; and &amp;#39;name_directory_description&amp;#39; parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-1866</guid>
    </item>
    <item>
      <title>GHSA-wj7p-g9vc-3935</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wj7p-g9vc-3935</link>
      <description>&lt;p&gt;The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin&amp;#39;s sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the &amp;#39;name_directory_name&amp;#39; and &amp;#39;name_directory_description&amp;#39; parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin&amp;#39;s sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the &amp;#39;name_directory_name&amp;#39; and &amp;#39;name_directory_description&amp;#39; parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wj7p-g9vc-3935</guid>
    </item>
  </channel>
</rss>
