(CVE-2026-126745)
Vulnerability from drupal – Published: 2026-11-11 18:05 – Updated: 2026-11-11 18:20 – Source websiteThis 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.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c2.0.1"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/realname"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c2.0.1"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "2.0.1"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-126745"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/shawn_smiley"
],
"name": "Shawn Smiley (shawn_smiley)"
}
],
"details": "This module enables you to display users by a configurable \"real name\" pattern built from tokens, instead of by their username.\n\nThe module does not sufficiently sanitize user input used in name patterns. \nA user can place Twig syntax in their own profile data and have it evaluated when their name is displayed.\n\nThis 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.",
"id": "DRUPAL-CONTRIB-2026-336",
"modified": "2026-11-11T18:20:08.000Z",
"published": "2026-11-11T18:05:10.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-336"
}
],
"schema_version": "1.7.0"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.