<?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>Tue, 13 Oct 2026 06:27:04 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-340999</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-340999</link>
      <description>EUVD-2026-340999</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-340999</guid>
    </item>
    <item>
      <title>fkie_cve-2026-12497</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-12497</link>
      <description>&lt;p&gt;The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile &amp;amp; Restrict Content  WordPress plugin before 4.16.18 does not consistently enforce the role restriction configured on its front-end registration role-selection field. The set of roles offered to the visitor and the set of roles the registration handler accepts are derived by two different parsers, and for some valid ways of configuring the offered roles the handler ignores the restriction and falls back to accepting any non-administrator role. Combined with the absence of a nonce on the public registration handler, this allows an unauthenticated visitor to register an account with a higher role, such as Editor or Author, than the form was configured to offer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile &amp;amp; Restrict Content  WordPress plugin before 4.16.18 does not consistently enforce the role restriction configured on its front-end registration role-selection field. The set of roles offered to the visitor and the set of roles the registration handler accepts are derived by two different parsers, and for some valid ways of configuring the offered roles the handler ignores the restriction and falls back to accepting any non-administrator role. Combined with the absence of a nonce on the public registration handler, this allows an unauthenticated visitor to register an account with a higher role, such as Editor or Author, than the form was configured to offer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-12497</guid>
    </item>
    <item>
      <title>GHSA-qw3x-5xr6-mfgm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qw3x-5xr6-mfgm</link>
      <description>&lt;p&gt;The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile &amp;amp; Restrict Content  WordPress plugin before 4.16.18 does not consistently enforce the role restriction configured on its front-end registration role-selection field. The set of roles offered to the visitor and the set of roles the registration handler accepts are derived by two different parsers, and for some valid ways of configuring the offered roles the handler ignores the restriction and falls back to accepting any non-administrator role. Combined with the absence of a nonce on the public registration handler, this allows an unauthenticated visitor to register an account with a higher role, such as Editor or Author, than the form was configured to offer.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The Paid Membership Plugin, Ecommerce, User Registration Form, Login Form, User Profile &amp;amp; Restrict Content  WordPress plugin before 4.16.18 does not consistently enforce the role restriction configured on its front-end registration role-selection field. The set of roles offered to the visitor and the set of roles the registration handler accepts are derived by two different parsers, and for some valid ways of configuring the offered roles the handler ignores the restriction and falls back to accepting any non-administrator role. Combined with the absence of a nonce on the public registration handler, this allows an unauthenticated visitor to register an account with a higher role, such as Editor or Author, than the form was configured to offer.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qw3x-5xr6-mfgm</guid>
    </item>
  </channel>
</rss>
