<?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 18:04:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43880 — WWBN AVideo: Unauthenticated Arbitrary Email Sending via sendEmail.json.php Allows Phishing from Site's Legitimate From…</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-43880</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WWBN AVideo&lt;/p&gt;
&lt;p&gt;WWBN AVideo is an open source video platform. In versions up to and including 29.0, objects/sendEmail.json.php exposes two branches depending on whether contactForm=1 is submitted. When the parameter is omitted, the endpoint sets $sendTo to an attacker-supplied email and, for unauthenticated callers, uses the site&amp;#39;s own contact email as the message From:/Reply-To:. The endpoint is explicitly allow-listed as a &amp;#34;public write action&amp;#34; in objects/functionsSecurity.php (line 885), so it requires no authentication or CSRF token. An unauthenticated attacker (solving a captcha) can force the site&amp;#39;s own SMTP infrastructure to send attacker-composed emails to arbitrary recipients with the site&amp;#39;s legitimate sender address, passing SPF/DKIM/DMARC for the site&amp;#39;s domain — ideal for targeted phishing and brand impersonation. Commit 4e3709895857a5857f0edb46b0ee984de0d9e1a2 contains an updated fix.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WWBN AVideo&lt;/p&gt;
&lt;p&gt;WWBN AVideo is an open source video platform. In versions up to and including 29.0, objects/sendEmail.json.php exposes two branches depending on whether contactForm=1 is submitted. When the parameter is omitted, the endpoint sets $sendTo to an attacker-supplied email and, for unauthenticated callers, uses the site&amp;#39;s own contact email as the message From:/Reply-To:. The endpoint is explicitly allow-listed as a &amp;#34;public write action&amp;#34; in objects/functionsSecurity.php (line 885), so it requires no authentication or CSRF token. An unauthenticated attacker (solving a captcha) can force the site&amp;#39;s own SMTP infrastructure to send attacker-composed emails to arbitrary recipients with the site&amp;#39;s legitimate sender address, passing SPF/DKIM/DMARC for the site&amp;#39;s domain — ideal for targeted phishing and brand impersonation. Commit 4e3709895857a5857f0edb46b0ee984de0d9e1a2 contains an updated fix.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-43880</guid>
    </item>
  </channel>
</rss>
