SA-CONTRIB-2026-336: Critical severity composer/drupal/realname vulnerability
This module enables you to display users by a configurable "real name" pattern built from tokens, instead of by their username. The module does not sufficiently sanitize user input used in name patterns. A user can place Twig syntax in their own profile data and have it evaluated when their name is displayed. This vulnerability is mitigated by the fact that the site must be configured with a real name pattern that includes user-supplied data, and the attacker must be able to edit that data on their own account.
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/drupal/realnameto a version that resolves this vulnerability.Fixed in 2.0.1
Event History
Frequently Asked Questions
Which deployments are affected in practice?
Exposure requires a configured real-name pattern that incorporates user-supplied profile data. Deployments without such a pattern are mitigated by the stated configuration requirement.
What does an attacker need to exploit this issue?
The attacker must be able to edit the profile data on their own account and enter Twig syntax into data used by the configured name pattern.
How can an administrator assess whether their configuration is exposed?
Review the configured real-name pattern and determine whether it includes fields that users can edit in their own profiles. If it does, user-provided values in those fields can be evaluated when the user's name is displayed.