CVE-2023-41336

Prevent injection of invalid entity ids for "autocomplete" fields

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.

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.

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2023-41336 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.11.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been fixed in symfony/ux-autocomplete version 2.11.2.

1. What is CVE-2023-41336? CVE-2023-41336 is a medium-severity improper input validation vulnerability in symfony/ux-autocomplete (composer), affecting versions < 2.11.2. It is fixed in 2.11.2. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2023-41336? CVE-2023-41336 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of symfony/ux-autocomplete are affected by CVE-2023-41336? symfony/ux-autocomplete (composer) versions < 2.11.2 is affected.
4. Is there a fix for CVE-2023-41336? Yes. CVE-2023-41336 is fixed in 2.11.2. Upgrade to this version or later.
5. Is CVE-2023-41336 exploitable, and should I be worried? Whether CVE-2023-41336 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-41336 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-41336? Upgrade symfony/ux-autocomplete to 2.11.2 or later.

Other vulnerabilities in symfony/ux-autocomplete