typo3-appointments vulnerable to Cross-site ScriptingGHSA-cf5r-3pvm-w64w
MEDIUMFix: innologi/typo3-appointments@986d3cbGHSA-cf5r-3pvm-w64w is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in innologi/typo3-appointments. A fix is available for innologi/typo3-appointments — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
innologi/typo3-appointmentsReal-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
A vulnerability, which was classified as problematic, was found in innologi appointments Extension up to 2.0.5 on TYPO3. This affects an unknown part of the component Appointment Handler. The manipulation of the argument formfield leads to cross site scripting. It is possible to initiate the attack remotely. Upgrading to version 2.0.6 is able to address this issue. The identifier of the patch is 986d3cb34e5e086c6f04e061f600ffc5837abe7f. It is recommended to upgrade the affected component. The identifier VDB-217353 was assigned to this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | innologi/typo3-appointments | all versions | 2.0.6composer require innologi/typo3-appointments:^2.0.6 |
Affected Products
appointment schedulerinnologiDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for innologi/typo3-appointments, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update innologi/typo3-appointments to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cf5r-3pvm-w64w 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
Is GHSA-cf5r-3pvm-w64w in your dependencies?
Find it across Packagist, including transitive dependencies.