# CVE-2026-101127: Joomla Extension - balbooa.com - Unauthenticated upload filename stored XSS in Balbooa Forms < 2.4.3.4

> An attacker can inject malicious scripts via uploaded filenames, leading to XSS when administrators view submissions in the Balbooa Forms extension.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-r586-6h3h-vc7q

## What is CVE-2026-101127?

CVE-2026-101127 is a high-severity cross-site scripting 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, and only if a user opens a file or follows a link.

### Official description

Joomla Extension - balbooa.com - Unauthenticated upload filename stored XSS in Balbooa Forms < 2.4.3.4 - The public form upload endpoint validates the uploaded file's extension and detected MIME type, but stores the attacker-supplied original multipart filename verbatim in `#__baforms_submissions_attachments.name`. A later anonymous form submission associates that temporary attachment with the newly created submission. When an administrator opens the submission, the component's JavaScript retrieves the stored attachment record and concatenates `file.name` directly into an HTML string. The complete string is assigned to `innerHTML`.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Balbooa Forms.

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

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

## Is CVE-2026-101127 being exploited?

There is no known exploitation of CVE-2026-101127 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-102424](https://insights.sbomify.com/CVE-2026-102424/): Path traversal in Balbooa Forms extension for Joomla (high 8.9)
- [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-101127 and fix it if it is affected.

What it is: CVE-2026-101127 is a high-severity cross-site scripting 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-101127 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-101127/ (Markdown: https://insights.sbomify.com/CVE-2026-101127/index.md)
```

## Sources

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

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