CVE-2026-67364: Balbooa Forms extension for Joomla · Code Injection
Affects Balbooa Forms extension for JoomlaSource CVE Database V5
Not known to be exploited · CVSS 10.0 Critical · fixed in 2.4.3.2 : patch Balbooa Forms extension for Joomla as a priority.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.4.3.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| balbooa.comBalbooa Forms extension for Joomla | Affected
| Fixed in– |
AI-suggested
A fix is available in Balbooa Forms version 2.4.3.2. Users should upgrade to version 2.4.3.2 or later to remediate this vulnerability. Until patched, ensure that forms do not use custom PHP post-submission handlers referencing the vulnerable shortcode and implement reCAPTCHA on submit buttons to reduce risk. Verify the vendor advisory for the latest remediation guidance.
Description
Joomla Extension - balbooa.com - Pre-auth PHP Code Injection in Balbooa Forms < 2.4.3.2 - The form'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.