<?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>Sun, 04 Oct 2026 22:38:43 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-67364 — Joomla Extension - balbooa.com - Pre-auth PHP Code Injection in Balbooa Forms &lt; 2.4.3.2</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-67364</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; balbooa.com Balbooa Forms extension for Joomla&lt;/p&gt;
&lt;p&gt;Joomla Extension - balbooa.com - Pre-auth PHP Code Injection in Balbooa Forms &amp;lt; 2.4.3.2 - The form&amp;#39;s optional custom-PHP post-submission handler is executed via eval(). The [URL parameter = X] shortcode is substituted with the raw, unescaped value of a query parameter, letting an unauthenticated attacker inject arbitrary PHP that executes server-side. The CSRF token needed to reach the endpoint is itself disclosed anonymously via a separate task, so it provides no real protection. Exploitability requires the form to have a custom-PHP handler configured (a documented builder feature) referencing that shortcode, and no reCAPTCHA on the submit button.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; balbooa.com Balbooa Forms extension for Joomla&lt;/p&gt;
&lt;p&gt;Joomla Extension - balbooa.com - Pre-auth PHP Code Injection in Balbooa Forms &amp;lt; 2.4.3.2 - The form&amp;#39;s optional custom-PHP post-submission handler is executed via eval(). The [URL parameter = X] shortcode is substituted with the raw, unescaped value of a query parameter, letting an unauthenticated attacker inject arbitrary PHP that executes server-side. The CSRF token needed to reach the endpoint is itself disclosed anonymously via a separate task, so it provides no real protection. Exploitability requires the form to have a custom-PHP handler configured (a documented builder feature) referencing that shortcode, and no reCAPTCHA on the submit button.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-67364</guid>
    </item>
  </channel>
</rss>
