How severe is CVE-2025-10316?

No CVSS score has been assigned to CVE-2025-10316 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-10316?

CVE-2025-10316 affects the following packages: lavitto/typo3-form-to-database (Packagist), lavitto/typo3-form-to-database (Packagist), lavitto/typo3-form-to-database (Packagist), lavitto/typo3-form-to-database (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2025-10316?

Update lavitto/typo3-form-to-database to 2.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10316 is resolved across your whole dependency graph.

How do I detect CVE-2025-10316 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lavitto/typo3-form-to-database, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-10316 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2025-10316 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-10316 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-10316?

CVE-2025-10316 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 27th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-10316?

CVE-2025-10316 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2025-10316 published, and has it been updated?

CVE-2025-10316 was published on September 16, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2025-10316 — typo3-form-to-database

CVE-2025-10316 is a Cross-site Scripting (XSS) vulnerability in lavitto/typo3-form-to-database. A fix is available for lavitto/typo3-form-to-database — see the affected versions and patch details below.

Cross-Site Scripting in extension "Form to Database" (form_to_database)

Also known asGHSA-54pg-2x9h-cmx8

Published

Sep 16, 2025

Updated

Oct 28, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-10316.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘lavitto/typo3-form-to-database🐘lavitto/typo3-form-to-database🐘lavitto/typo3-form-to-database🐘lavitto/typo3-form-to-database

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`lavitto/typo3-form-to-database`	all versions	2.2.5`composer require lavitto/typo3-form-to-database:^2.2.5`
🐘Packagist	`lavitto/typo3-form-to-database`	≥ 3.0.0&&< 3.2.2	3.2.2`composer require lavitto/typo3-form-to-database:^3.2.2`
🐘Packagist	`lavitto/typo3-form-to-database`	≥ 4.0.0&&< 4.2.3	4.2.3`composer require lavitto/typo3-form-to-database:^4.2.3`
🐘Packagist	`lavitto/typo3-form-to-database`	≥ 5.0.0&&< 5.0.2	5.0.2`composer require lavitto/typo3-form-to-database:^5.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lavitto/typo3-form-to-database, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lavitto/typo3-form-to-database to 2.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-10316 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-10316 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works