<?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 04:21:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-12770 — New User Approve &lt;= 3.0.9 - Unauthenticated Sensitive Information Disclosure via Type Juggling</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-12770</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; saadiqbal New User Approve&lt;/p&gt;
&lt;p&gt;The New User Approve plugin for WordPress is vulnerable to unauthorized data disclosure in all versions up to, and including, 3.0.9 due to insufficient API key validation using loose equality comparison. This makes it possible for unauthenticated attackers to retrieve personally identifiable information (PII), including usernames and email addresses of users with various approval statuses via the Zapier REST API endpoints, by exploiting PHP type juggling with the api_key parameter set to &amp;#34;0&amp;#34; on sites where the Zapier API key has not been configured.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; saadiqbal New User Approve&lt;/p&gt;
&lt;p&gt;The New User Approve plugin for WordPress is vulnerable to unauthorized data disclosure in all versions up to, and including, 3.0.9 due to insufficient API key validation using loose equality comparison. This makes it possible for unauthenticated attackers to retrieve personally identifiable information (PII), including usernames and email addresses of users with various approval statuses via the Zapier REST API endpoints, by exploiting PHP type juggling with the api_key parameter set to &amp;#34;0&amp;#34; on sites where the Zapier API key has not been configured.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-12770</guid>
    </item>
  </channel>
</rss>
