CVE-2026-126745: 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.
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 sites are exposed to exploitation?
Exposure requires a configured real name pattern that incorporates user-supplied profile data. Sites that do not use such a pattern are mitigated by this condition.
What does an attacker need to exploit this issue?
The attacker must be able to edit the relevant data on their own user account and place Twig syntax in that profile data. The injected syntax is evaluated when the user's name is displayed.
How can administrators assess whether their configuration is affected?
Review the module's configured real name pattern and determine whether it includes fields users can edit in their own profiles. If it does, inspect whether profile values containing Twig syntax could be displayed through the real name output.