Balbooa Forms (com_baforms) below 2.4.3.4 - Unauthenticated PHP Code Injection (RCE), Local File Disclosure via Auto-Reply Attachments, Stored XSS and Attachment Deletion
Balbooa Forms before 2.4.3.4 (every release from 1.0.0 to 2.4.3.3, per the Joomla CNA) has five flaws, all reachable by an anonymous visitor through a public form. CVE-2026-102425 (CVSS 4.0 9.5): the optional post-submission PHP action replaces field shortcodes with the raw submitted value before eval(), so a form that uses a PHP action with a visitor-supplied shortcode inside a double-quoted string allows remote code execution. CVE-2026-102424 (8.9): on a form with auto-reply and attach-uploaded-files enabled, a guest can submit a traversal filename such as ../../../../configuration.php and receive any file readable by the site in the auto-reply email. CVE-2026-101127 (8.6): the original upload filename is stored verbatim and rendered into the administrator submission view, giving stored XSS against administrators. CVE-2026-101112 (6.9): removeTmpAttachment deletes any attachment by ID without binding it to the uploader session. CVE-2026-101126 (6.9): final submission trusts client-supplied attachment filenames and display names, allowing cross-session claiming and tampering. Reported by Sergiy Tryzhychynskyi and Lukasz Rybak, coordinated by the Joomla Security Strike Team. Update Balbooa Forms to 2.4.3.4 or later and confirm the component reports 2.4.3.4. If a form sent attachments in auto-replies, rotate the database password in configuration.php. Versions below 2.4.3.2 are also affected by the earlier CVSS 10.0 Balbooa Forms advisories.
Affected versions: < 2.4.3.4
Full advisory: our disclosure post
Balbooa Forms (com_baforms) 2.4.3 to below 2.4.3.2 - Unauthenticated PHP Code Injection (RCE, CVSS 10.0) and Unauthenticated Payment Amount Tampering
Balbooa Forms 2.4.3 and 2.4.3.1 are affected by two unauthenticated flaws fixed in 2.4.3.2 on 18 August 2026 and published as CVEs by the Joomla CNA on 19 August 2026. CVE-2026-67364 (CWE-94 / CWE-95, CVSS 4.0 base 10.0 Critical, CVSS 3.1 9.8, AV:N/AC:L/PR:N/UI:N) is a pre-auth PHP code injection: the form's optional custom-PHP post-submission handler is executed through eval(), and the [URL parameter = X] shortcode is substituted with the raw, unescaped value of a query parameter, so an unauthenticated visitor can inject arbitrary PHP that runs server-side. The CSRF token needed to reach the endpoint is itself disclosed anonymously through a separate task, so it provides no real protection. Exploitation requires the form to have a custom-PHP handler configured (a documented form-builder feature) that references that shortcode, and no reCAPTCHA on the submit button, so not every install on these versions is exploitable - but that precondition is an ordinary builder setting and cannot be ruled out remotely. CVE-2026-67363 (CWE-472 / CWE-602, CVSS 4.0 base 7.7 High) is pre-auth payment amount tampering: the stripeCharges and payAuthorize endpoints accept the charge total from a client-controlled request parameter and forward it to the payment gateway without recomputing it from the form's configured product prices, and neither endpoint enforces authentication or a CSRF check. An unauthenticated attacker can purchase any priced item for an arbitrary amount such as 0.01, and can additionally forge line items, quantities and shipping. Both CVE records give the affected range as 1.0.0 to 2.4.3.1. Balbooa originally presented 2.4.3.2 as routine hardening covering the Media Manager, path validation, payment validation, post-submission PHP scripts and signature image validation, and stated it was not related to any publicly disclosed vulnerability; these CVE records supersede that description, and two of those five areas are the ones above. This rule starts at 2.4.3 because it also absorbs the 2.4.3.1 hardening release of 31 July 2026, so a site on 2.4.3 is missing both sets of fixes. Update to Balbooa Forms 2.4.3.4 or later, which also includes the further security fixes released on 29 September 2026. If the site publishes a form with a custom-PHP post-submission handler, treat it as potentially compromised until checked: look for unfamiliar administrator accounts and for stray .php files under the upload folder (by default images/baforms/uploads/). If the site takes payments through a Balbooa form, reconcile recent Stripe or Authorize.Net transactions against the configured product prices. Everything up to and including 2.4.2.1 is covered by a separate rule carrying CVE-2026-65880 and CVE-2026-56291. Both of these CVEs are credited to Akinlabi Omoogun; neither was a mySites.guru finding.
Affected versions: ≥ 2.4.3 and < 2.4.3.2
Full advisory: www.cve.org
Balbooa Forms (com_baforms) <= 2.4.2.1 - Unauthenticated Remote Code Execution (CVSS 10.0) and Arbitrary File Upload
Balbooa Forms up to and including 2.4.2.1 is affected by an unauthenticated remote code execution flaw (CVE-2026-65880, CVSS 4.0 base 10.0, AV:N/AC:L/PR:N/UI:N with high impact on confidentiality, integrity and availability across the security scope). Insecure form processing logic allows code execution on any form that includes the signature field type, with no login and no user interaction. Fixed in Balbooa Forms 2.4.3 - but 2.4.3 is no longer a safe ceiling, because CVE-2026-67364 (pre-auth PHP code injection, CVSS 10.0) and CVE-2026-67363 (pre-auth payment amount tampering, CVSS 7.7) affect 1.0.0 through 2.4.3.1 and were fixed in 2.4.3.2 on 18 August 2026, making 2.4.3.2 the current minimum safe version. This rule also covers two earlier flaws in the same component: CVE-2026-56291, an unauthenticated arbitrary file upload (RCE) in versions up to and including 2.4.0 - the frontend attachment upload accepted a file from any anonymous visitor with no login, no CSRF token and no allow-list on the file extension, and because it trusted the caller-supplied filename a .php upload was written to a public directory (by default images/baforms/uploads/) and could then be executed (CWE-434); and CVE-2025-49485, an SQL injection via the id parameter in 1.0.0 to 2.3.1.1, exploitable by privileged users. Update every Balbooa Forms install to 2.4.3.4 or later, which also includes the further security fixes released on 29 September 2026. Then check the upload folder for stray .php files and the Joomla user list for unfamiliar administrator accounts. Any site that was internet-facing on 2.4.2.1 or earlier with a signature-field form published should be treated as potentially compromised until it has been updated and checked. Also within this rule: CVE-2021-47930 (Balbooa Forms Builder 2.0.6 arbitrary file upload), which sits below this ceiling and needs no separate row.
Affected versions: ≤ 2.4.2.1
Full advisory: www.balbooa.com
Running Balbooa Forms on a site you manage?
A free audit tells you which of your Joomla and WordPress sites run an affected version, which are out of date, and which have not been backed up. No card required. If a site is already compromised, fix.mysites.guru is a single fixed fee per incident, usually resolved the same day.
CVE identifiers: CVE-2026-102425, CVE-2026-102424, CVE-2026-101127, CVE-2026-101112, CVE-2026-101126, CVE-2026-67364, CVE-2026-67363, CVE-2026-65880, CVE-2026-56291, CVE-2025-49485. Rules current as of 3 October 2026.