# CVE-2026-102424: Path traversal in Balbooa Forms extension for Joomla

> Unauthenticated attackers can exfiltrate local files via path traversal in Balbooa Forms auto-reply attachments when specific options are enabled.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **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-j3r3-fqf7-gc2r

## What is CVE-2026-102424?

CVE-2026-102424 is a high-severity path traversal 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 path traversal exfiltrates local files through auto-reply attachments in Balbooa Forms < 2.4.3.4 - Balbooa Forms accepts upload-field state as Guest-controlled JSON during public form submission. For every object whose `id` merely looks numeric, the component trusts the supplied `filename`, concatenates it below the configured upload directory, and adds the result to an array of local attachment paths. It does not load the referenced attachment row, verify ownership/session/form/field, require that the ID exists, canonicalize the path, or enforce containment. If the form's normal “auto reply” and “attach uploaded files” options are enabled, the component sends those local paths as email attachments to the address submitted in an email field. A Guest can therefore submit a nonexistent numeric ID plus a traversal filename such as `../../../../configuration.php` and receive any file readable by the Joomla process.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Balbooa Forms.

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

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

## Is CVE-2026-102424 being exploited?

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

## 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-102425](https://insights.sbomify.com/CVE-2026-102425/): Joomla Extension - balbooa.com - Unauthenticated RCE via field shortcode injection in Balbooa Forms < 2.4.3.4 (critical 9.5)
- [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-102424 and fix it if it is affected.

What it is: CVE-2026-102424 is a high-severity path traversal 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-102424 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-102424/ (Markdown: https://insights.sbomify.com/CVE-2026-102424/index.md)
```

## Sources

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

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