<?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:04:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-8853 — MW WP Form &lt;= 5.1.3 - Authenticated (Editor+) Stored Cross-Site Scripting via 'memo' Parameter</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-8853</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; websoudan MW WP Form&lt;/p&gt;
&lt;p&gt;The MW WP Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;memo&amp;#39; parameter in all versions up to, and including, 5.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the memo value is stored via update_post_meta() rather than wp_insert_post(), WordPress&amp;#39;s built-in kses and unfiltered_html protections do not apply, allowing attackers to break out of the textarea element via injected closing tags regardless of role-based content filtering.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; websoudan MW WP Form&lt;/p&gt;
&lt;p&gt;The MW WP Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;memo&amp;#39; parameter in all versions up to, and including, 5.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the memo value is stored via update_post_meta() rather than wp_insert_post(), WordPress&amp;#39;s built-in kses and unfiltered_html protections do not apply, allowing attackers to break out of the textarea element via injected closing tags regardless of role-based content filtering.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-8853</guid>
    </item>
  </channel>
</rss>
