# CVE-2025-10316: Cross-Site Scripting in extension "Form to Database" (form_to_database)

> Cross-Site Scripting in the TYPO3 Form to Database extension allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/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:** Yes
- **Published:** 16 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** GHSA-54pg-2x9h-cmx8

## What is CVE-2025-10316?

CVE-2025-10316 is a low-severity cross-site scripting vulnerability in TYPO3 Extension "Form to Database" (form_to_database), published on 16 Sep 2025. 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

The extension "Form to Database" is susceptible to Cross-Site Scripting. This issue affects the following versions: before 2.2.5, from 3.0.0 before 3.2.2, from 4.0.0 before 4.2.3, from 5.0.0 before 5.0.2.

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

## Which versions are affected by CVE-2025-10316?

8 open source packages ship an affected version, including lavitto/typo3-form-to-database.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lavitto/typo3-form-to-database` | Packagist | All versions | 2.2.5 |
| `lavitto/typo3-form-to-database` | Packagist | All versions | 2.2.5 |
| `lavitto/typo3-form-to-database` | Packagist | From 3.0.0 | 3.2.2 |
| `lavitto/typo3-form-to-database` | Packagist | From 3.0.0 | 3.2.2 |
| `lavitto/typo3-form-to-database` | Packagist | From 4.0.0 | 4.2.3 |
| `lavitto/typo3-form-to-database` | Packagist | From 4.0.0 | 4.2.3 |
| `lavitto/typo3-form-to-database` | Packagist | From 5.0.0 | 5.0.2 |
| `lavitto/typo3-form-to-database` | Packagist | From 5.0.0 | 5.0.2 |

## How do I fix CVE-2025-10316?

Upgrade lavitto/typo3-form-to-database to a fixed version for your release line: 2.2.5, 3.2.2, 4.2.3 or 5.0.2.

## Is CVE-2025-10316 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10316 and fix it if it is affected.

What it is: CVE-2025-10316 is a low-severity cross-site scripting vulnerability in TYPO3 Extension "Form to Database" (form_to_database), published on 16 Sep 2025. 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-2025-10316 in the wild and no public exploit code.

Affected packages and fixed versions:
- lavitto/typo3-form-to-database (Packagist): affected all versions; fixed in 2.2.5
- lavitto/typo3-form-to-database (Packagist): affected all versions; fixed in 2.2.5
- lavitto/typo3-form-to-database (Packagist): affected from 3.0.0; fixed in 3.2.2
- lavitto/typo3-form-to-database (Packagist): affected from 3.0.0; fixed in 3.2.2
- lavitto/typo3-form-to-database (Packagist): affected from 4.0.0; fixed in 4.2.3
- lavitto/typo3-form-to-database (Packagist): affected from 4.0.0; fixed in 4.2.3
- lavitto/typo3-form-to-database (Packagist): affected from 5.0.0; fixed in 5.0.2
- lavitto/typo3-form-to-database (Packagist): affected from 5.0.0; fixed in 5.0.2

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

## Sources

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

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