<?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>Mon, 12 Oct 2026 23:41:24 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-8787 — Firebase Support &amp; Chat Management &lt;= 3.1.1 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-8787</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; devsabbirahmed Firebase Support &amp;amp; Chat Management&lt;/p&gt;
&lt;p&gt;The Firebase Support &amp;amp; Chat Management plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 3.1.1. This is due to the `firebase_auth()` function authenticating the request as the WordPress user whose email is supplied in the `user_email` POST parameter without verifying ownership of that email (no Firebase ID token signature/issuer/audience verification). This makes it possible for authenticated attackers, with Subscriber-level access and above, to log in as an arbitrary existing user — including an Administrator — by submitting that user&amp;#39;s email address to the `acb_firebase_auth` AJAX action, resulting in full account takeover.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; devsabbirahmed Firebase Support &amp;amp; Chat Management&lt;/p&gt;
&lt;p&gt;The Firebase Support &amp;amp; Chat Management plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 3.1.1. This is due to the `firebase_auth()` function authenticating the request as the WordPress user whose email is supplied in the `user_email` POST parameter without verifying ownership of that email (no Firebase ID token signature/issuer/audience verification). This makes it possible for authenticated attackers, with Subscriber-level access and above, to log in as an arbitrary existing user — including an Administrator — by submitting that user&amp;#39;s email address to the `acb_firebase_auth` AJAX action, resulting in full account takeover.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-8787</guid>
    </item>
  </channel>
</rss>
