CVE-2026-122073: Stored XSS in Drupal Name Field
The Drupal Name Field module before version 1.6.0 insufficiently sanitizes stored name values under some circumstances. A crafted name value can be interpreted as HTML when rendered, resulting in stored cross-site scripting in a user's browser.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Malicious script execution in an affected user's browser can compromise the confidentiality and integrity of data accessible to that user. The vulnerability is rated moderately critical (12/25).
Remediation
Patch, then assume compromise.
Upgrade the Drupal Name Field module to release 8.x-1.6 or a later fixed release.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-122073 exploited in the wild?
- As of Nov 4, 2026, Mallory has no reports of CVE-2026-122073 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-122073?
- As of Nov 4, 2026, Mallory has found no public exploit for CVE-2026-122073.
- Is there a patch for CVE-2026-122073?
- Upgrade the Drupal Name Field module to release 8.x-1.6 or a later fixed release.
Recent activity
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.