First published: Mon Sep 11 2023(Updated: )
### Impact Under certain circumstances, an attacker could successfully submit an entity id for an `EntityType` that is *not* part of the valid choices. Affected applications are any that use: * A custom `query_builder` option to limit the valid results; AND * An `EntityType` with `'autocomplete' => true` or a custom [AsEntityAutocompleteField](https://symfony.com/bundles/ux-autocomplete/current/index.html#usage-in-a-form-with-ajax). Under this circumstance, if an id is submitted, it is accepted even if the matching record would not be returned by the custom query built with `query_builder`. ### Patches The problem has been fixed in `symfony/ux-autocomplete` version 2.11.2. ### Workarounds Upgrade to version 2.11.2 or greater of `symfony/ux-autocomplete` or perform extra validation after submit to verify the selected option is valid.
Credit: security-advisories@github.com security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Symfony Ux Autocomplete | <2.11.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
An attacker could submit an entity id that is not part of the valid choices.
Any application that uses a custom query_builder option to limit valid results and includes an EntityType with autocomplete enabled.
Update to version 2.11.2 of Symfony/ux-autocomplete package.
The severity is medium (CVSS score 6.5).
You can find more information at the following references: [link1](https://github.com/symfony/ux-autocomplete/security/advisories/GHSA-4cpv-669c-r79x), [link2](https://github.com/symfony/ux-autocomplete/commit/fabcb2eee14b9e84a45b276711853a560b5d770c), [link3](https://symfony.com/bundles/ux-autocomplete/current/index.html#usage-in-a-form-with-ajax).