This module enables you to link the output of a field to a URL or to the value of another field. The module doesn't sufficiently separate field content from te...

An attacker who can create or edit content in a field with Linked Field enabled in its display settings may be able to expose site configuration values, including API keys or credentials. The module does not sufficiently separate field content from template code when rendering linked field output. Whether configuration values can be exposed depends on the Twig extensions installed on the site.

Look for drupal/linked_field and its version in composer.lock. The advisory lists 1.8.0 as fixed but gives no affected version range. Check whether Linked Field is enabled in any field's display settings, which roles can create or edit content in those fields, and which Twig extensions are installed. The advisory does not name specific Twig extensions.

The vulnerability is mitigated by the requirement that an attacker have a role with permission to create or edit content in a field with Linked Field enabled in its display settings.

This module enables you to link the output of a field to a URL or to the value of another field.

The module doesn't sufficiently separate field content from template code when rendering linked field output. Depending on the Twig extensions installed on the site, this can be used to expose site configuration values, which may include sensitive information such as API keys or credentials.

This vulnerability is mitigated by the fact that an attacker must have a role with permission to create or edit content in a field that has Linked Field enabled in its display settings.