# CVE-2026-56291: Balbooa Forms Unrestricted Upload of File with Dangerous Type

> Unauthenticated attackers can upload executable files to the Balbooa Forms extension, leading to remote code execution.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A/AU:Y/U:Red`)
- **Exploited in the wild:** Yes, since 10 Jul 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-28f5-j5p5-xmmw

## What is CVE-2026-56291?

CVE-2026-56291 is a critical vulnerability in balbooa.com Balbooa Forms extension for Joomla, published on 9 Jul 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 file upload in Balbooa Forms extension < 2.4.1 - The Joomla extension Balbooa Forms is vulnerable to an unauthenticated arbitrary file upload that allows uploading executable files and leads to full RCE.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Balbooa Forms.

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

No fix has been published for CVE-2026-56291 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 13 Jul 2026.

## Is CVE-2026-56291 being exploited?

Yes. Attackers have exploited CVE-2026-56291 in the wild since at least 10 Jul 2026.

Public exploit code:

- Balbooa Forms (com_baforms) < 2.4.1 — Unauthenticated File Upload to RCE via form.uploadAttachmentFile | CVSS 9.8 | CISA KEV (github_poc): https://github.com/shinthink/CVE-2026-56291
- Mendeteksi versi (passive detection) & Exploitation CVE POC (github_poc): https://github.com/0xdenis77/CVE-2026-56291
- nuclei template for CVE-2026-56291 (github_poc): https://github.com/rimbadirgantara/CVE-2026-56291.yaml
- The Joomla extension Balbooa Forms is vulnerable to an unauthenticated arbitrary file upload that allows uploading executable files and leads to full RCE. (github_poc): https://github.com/ChiefYoru/CVE-2026-56291_PoC
- https://github.com/theendofabbys/CVE-2026-56291 (github_poc): https://github.com/theendofabbys/CVE-2026-56291
- Balbooa Forms < 2.4.1 - Unauthenticated Arbitrary File Upload (nuclei): http/cves/2026/CVE-2026-56291.yaml

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

- [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-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-56291 and fix it if it is affected.

What it is: CVE-2026-56291 is a critical vulnerability in balbooa.com Balbooa Forms extension for Joomla, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-56291 in the wild since at least 10 Jul 2026.

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-56291/ (Markdown: https://insights.sbomify.com/CVE-2026-56291/index.md)
```

## Sources

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

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