<?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://db.gcve.eu</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, 11 Nov 2026 15:29:11 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-120550</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-120550</link>
      <description>&lt;p&gt;The WP User Manager – Registration Form, Login Form, User Profile Builder &amp;amp; Member Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;name (REST users endpoint) -&amp;gt; wp_users.display_name&amp;#39; parameter in all versions up to, and including, 2.10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored via the WordPress core REST endpoint POST /wp-json/wp/v2/users/me, which bypasses the plugin&amp;#39;s own wpum_sanitize_text sanitizer applied on its front-end account form, making the save-time sanitization ineffective as a mitigation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP User Manager – Registration Form, Login Form, User Profile Builder &amp;amp; Member Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;name (REST users endpoint) -&amp;gt; wp_users.display_name&amp;#39; parameter in all versions up to, and including, 2.10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored via the WordPress core REST endpoint POST /wp-json/wp/v2/users/me, which bypasses the plugin&amp;#39;s own wpum_sanitize_text sanitizer applied on its front-end account form, making the save-time sanitization ineffective as a mitigation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-120550</guid>
    </item>
    <item>
      <title>GHSA-q737-h7j9-qw8g</title>
      <link>https://db.gcve.eu/vuln/ghsa-q737-h7j9-qw8g</link>
      <description>&lt;p&gt;The WP User Manager – Registration Form, Login Form, User Profile Builder &amp;amp; Member Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;name (REST users endpoint) -&amp;gt; wp_users.display_name&amp;#39; parameter in all versions up to, and including, 2.10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored via the WordPress core REST endpoint POST /wp-json/wp/v2/users/me, which bypasses the plugin&amp;#39;s own wpum_sanitize_text sanitizer applied on its front-end account form, making the save-time sanitization ineffective as a mitigation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The WP User Manager – Registration Form, Login Form, User Profile Builder &amp;amp; Member Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;name (REST users endpoint) -&amp;gt; wp_users.display_name&amp;#39; parameter in all versions up to, and including, 2.10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is stored via the WordPress core REST endpoint POST /wp-json/wp/v2/users/me, which bypasses the plugin&amp;#39;s own wpum_sanitize_text sanitizer applied on its front-end account form, making the save-time sanitization ineffective as a mitigation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-q737-h7j9-qw8g</guid>
    </item>
  </channel>
</rss>
