CVE-2025-10316 — lavitto/typo3-form-to-dat…
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)
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
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
lavitto/typo3-form-to-database🐘lavitto/typo3-form-to-database🐘lavitto/typo3-form-to-database🐘lavitto/typo3-form-to-databaseReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | lavitto/typo3-form-to-database | all versions | 2.2.5composer require lavitto/typo3-form-to-database:^2.2.5 |
| 🐘Packagist | lavitto/typo3-form-to-database | ≥ 3.0.0&&< 3.2.2 | 3.2.2composer require lavitto/typo3-form-to-database:^3.2.2 |
| 🐘Packagist | lavitto/typo3-form-to-database | ≥ 4.0.0&&< 4.2.3 | 4.2.3composer require lavitto/typo3-form-to-database:^4.2.3 |
| 🐘Packagist | lavitto/typo3-form-to-database | ≥ 5.0.0&&< 5.0.2 | 5.0.2composer require lavitto/typo3-form-to-database:^5.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
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
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-10316 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-10316. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-10316 in your dependencies?
O3 Security finds CVE-2025-10316 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.