# CVE-2026-102425: Joomla Extension - balbooa.com - Unauthenticated RCE via field shortcode injection in Balbooa Forms < 2.4.3.4

> Unauthenticated attackers can execute arbitrary code by injecting PHP via form field shortcodes if the optional PHP-after-submission feature is enabled.

- **Severity:** Critical 9.5 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-r3hx-8v55-pg55

## What is CVE-2026-102425?

CVE-2026-102425 is a critical code injection vulnerability in balbooa.com Balbooa Forms extension for Joomla, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Joomla Extension - balbooa.com - Unauthenticated RCE via field shortcode injection in Balbooa Forms < 2.4.3.4 - Balbooa Forms supports administrator-defined PHP code which runs after a public form submission. The feature also supports form-field shortcodes inside that PHP. Before calling `eval()`, the component replaces each shortcode with the raw value submitted by the visitor, leading to an RCE vector. A public form must use the product's optional PHP-after-submission action and interpolate an attacker-controlled field shortcode inside a double-quoted PHP string to be vulnerable.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-102425?

It affects 1 product.


Products: Balbooa Forms.

## How do I fix CVE-2026-102425?

No fix has been published for CVE-2026-102425 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102425 being exploited?

There is no known exploitation of CVE-2026-102425 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-102425 PoC (PoCbit) — Joomla Balbooa Forms (com_baforms) <2.4.3.4 unauth RCE via field shortcode injection in post-submission PHP eval(). check + exploit + mass bulk. https://pocbit.org/pocs/cve-2026-102425 (github_poc): https://github.com/murrez/CVE-2026-102425
- CVE-2026-102425 - GUI CONSOLE (github_poc): https://github.com/tonydelouvre/CVE-2026-102425

## Other vulnerabilities in balbooa.com Balbooa Forms extension for Joomla

- [CVE-2026-56291](https://insights.sbomify.com/CVE-2026-56291/): Balbooa Forms Unrestricted Upload of File with Dangerous Type (critical 10.0, exploited in the wild)
- [CVE-2026-102424](https://insights.sbomify.com/CVE-2026-102424/): Path traversal in Balbooa Forms extension for Joomla (high 8.9)
- [CVE-2026-101127](https://insights.sbomify.com/CVE-2026-101127/): Joomla Extension - balbooa.com - Unauthenticated upload filename stored XSS in Balbooa Forms < 2.4.3.4 (high 8.6)
- [CVE-2026-101112](https://insights.sbomify.com/CVE-2026-101112/): Joomla Extension - balbooa.com - Unauthorized Deletion of Attachments in Balbooa Forms < 2.4.3.4 (medium 6.9)
- [CVE-2026-101126](https://insights.sbomify.com/CVE-2026-101126/): Joomla Extension - balbooa.com - File meta data tampering in Balbooa Forms < 2.4.3.4 (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102425 and fix it if it is affected.

What it is: CVE-2026-102425 is a critical code injection vulnerability in balbooa.com Balbooa Forms extension for Joomla, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102425 in the wild and no public exploit code.

Affected product: balbooa.com Balbooa Forms extension for Joomla. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102425/ (Markdown: https://insights.sbomify.com/CVE-2026-102425/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102425
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102425
- OSV: https://osv.dev/vulnerability/CVE-2026-102425

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102425/
Summaries are generated and may contain mistakes; the official description above is the record.