CVE-2023-46735 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in symfony/webhook. A fix is available for symfony/webhook — see the affected versions and patch details below.
Symfony potential Cross-site Scripting in WebhookController
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-2023-46735.
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
symfony/webhook🐘symfony/symfonyReal-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
Description
The error message in WebhookController returns unescaped user-submitted input.
Resolution
WebhookController now doesn't return any user-submitted input in its response.
The patch for this issue is available here for branch 6.3.
Credits
We would like to thank Maxime Aknin for reporting the issue and to Nicolas Grekas for providing the fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/webhook | ≥ 6.3.0&&< 6.3.8 | 6.3.8composer require symfony/webhook:^6.3.8 |
| 🐘Packagist | symfony/symfony | ≥ 6.3.0&&< 6.3.8 | 6.3.8composer require symfony/symfony:^6.3.8 |
Affected Products
symfonysensiolabsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/webhook, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/webhook to 6.3.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-46735 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 CVE-2023-46735 in your dependencies?
Find it across Packagist, including transitive dependencies.