<?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>Fri, 09 Oct 2026 05:21:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2021-24443 — Youzify &lt; 1.0.7 - Stored Cross-Site Scripting via Biography</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2021-24443</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Unknown Youzify – BuddyPress Community, User Profile, Social Network &amp;amp; Membership Plugin for WordPress&lt;/p&gt;
&lt;p&gt;The About Me widget of the Youzify – BuddyPress Community, User Profile, Social Network &amp;amp; Membership WordPress plugin before 1.0.7 does not properly sanitise its Biography field, allowing any authenticated user to set Cross-Site Scripting payloads in it, which will be executed when viewing the affected user profile. This could allow a low privilege user to gain unauthorised access to the admin side of the blog by targeting an admin, inducing them to view their profile with a malicious payload adding a rogue account for example.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Unknown Youzify – BuddyPress Community, User Profile, Social Network &amp;amp; Membership Plugin for WordPress&lt;/p&gt;
&lt;p&gt;The About Me widget of the Youzify – BuddyPress Community, User Profile, Social Network &amp;amp; Membership WordPress plugin before 1.0.7 does not properly sanitise its Biography field, allowing any authenticated user to set Cross-Site Scripting payloads in it, which will be executed when viewing the affected user profile. This could allow a low privilege user to gain unauthorised access to the admin side of the blog by targeting an admin, inducing them to view their profile with a malicious payload adding a rogue account for example.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2021-24443</guid>
    </item>
  </channel>
</rss>
