# CVE-2026-112240: Broken Access Control in extension "TYPO3 Fluid-Form by coding.ms" (fluid_form)


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-c6q3-3p3f-392w

## What is CVE-2026-112240?

CVE-2026-112240 is a medium-severity vulnerability in Extension "TYPO3 Fluid-Form by coding.ms", published on 20 Oct 2026. 

### Official description

The download link for files uploaded through a form relied on a token that could be predicted. The file name in the request was also not verified in a way that resisted guessing. An unauthenticated attacker could use this to access files uploaded by other visitors. In addition, the token was shown in plain text in the text version of the notification email.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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


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

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

## Is CVE-2026-112240 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112240 is a medium-severity vulnerability in Extension "TYPO3 Fluid-Form by coding.ms", published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112240 in the wild and no public exploit code.

Affected product: Extension "TYPO3 Fluid-Form by coding.ms". 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-112240/ (Markdown: https://insights.sbomify.com/CVE-2026-112240/index.md)
```

## Sources

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

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