Skip to main content
Vulnerability Database/CVE-2026-104396

CVE-2026-104396: Name Directory Stored XSS Vulnerability

CVE-2026-104396 is a stored cross-site scripting flaw in the Name Directory WordPress plugin that enables attackers to inject malicious scripts. This article covers technical details, affected versions through 1.34.2, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104396 Overview

CVE-2026-104396 is a stored Cross-Site Scripting (XSS) vulnerability in the Jeroen Peters Name Directory plugin for WordPress. The flaw stems from improper neutralization of user-supplied input during web page generation [CWE-79]. It affects all versions of Name Directory up to and including 1.34.2. An authenticated attacker with low privileges can inject malicious JavaScript that executes in the browsers of users who view the affected pages. Successful exploitation requires user interaction and can impact confidentiality, integrity, and availability within the victim's browser context.

Critical Impact

Stored XSS enables attackers to execute arbitrary JavaScript in visitors' browsers, hijack sessions, perform actions on behalf of administrators, and pivot to further compromise of the WordPress site.

Affected Products

  • Jeroen Peters Name Directory plugin for WordPress
  • All versions from n/a through 1.34.2
  • WordPress sites using the name-directory plugin

Discovery Timeline

  • 2026-10-05 - CVE-2026-104396 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-104396

Vulnerability Analysis

The vulnerability is a stored Cross-Site Scripting flaw within the Name Directory WordPress plugin. Stored XSS occurs when user-supplied input is persisted by the application and later rendered in a web page without proper encoding or sanitization. In this case, the plugin fails to neutralize script content submitted through plugin-controlled input fields before storing it and reflecting it back into generated pages.

When an administrator or visitor loads a page containing the injected payload, the attacker's JavaScript executes in the context of the WordPress site. This allows session theft, forced administrative actions, phishing overlays, and redirection to attacker-controlled infrastructure.

The scope is marked as changed, meaning the injected script executes beyond the vulnerable component's security boundary, affecting authenticated users across the WordPress application.

Root Cause

The root cause is missing or insufficient output encoding and input sanitization in the plugin's handling of directory entries or related configuration fields. The plugin stores attacker input verbatim and emits it into HTML contexts without applying WordPress escaping functions such as esc_html(), esc_attr(), or wp_kses().

Attack Vector

Exploitation requires an authenticated user with at least low-level privileges to submit a crafted payload containing JavaScript into a plugin input field. The payload is stored in the WordPress database. When a privileged user, such as an administrator reviewing submissions, loads the affected page, the script executes in their browser. User interaction is required to trigger the payload.

No verified public proof-of-concept code is available. Refer to the Patchstack XSS Vulnerability Report for the technical advisory.

Detection Methods for CVE-2026-104396

Indicators of Compromise

  • Unexpected <script> tags, javascript: URIs, or event handler attributes (onerror, onload) stored in Name Directory database entries.
  • WordPress administrator sessions originating from unfamiliar IP addresses shortly after viewing Name Directory pages.
  • Outbound HTTP requests from administrator browsers to unknown external domains when loading plugin pages.

Detection Strategies

  • Audit WordPress database tables used by the name-directory plugin for HTML or JavaScript content in fields intended for plain text.
  • Inspect web server access logs for POST requests to plugin endpoints containing encoded script payloads or suspicious character sequences.
  • Deploy a Web Application Firewall (WAF) rule set that identifies common XSS payload patterns targeting WordPress plugins.

Monitoring Recommendations

  • Monitor administrator account activity, including configuration changes, new user creation, and plugin installations following page visits.
  • Alert on anomalous JavaScript execution or Content Security Policy (CSP) violations reported from WordPress admin pages.
  • Track plugin version inventory across WordPress deployments to confirm all instances are patched.

How to Mitigate CVE-2026-104396

Immediate Actions Required

  • Identify all WordPress sites running the Name Directory plugin at version 1.34.2 or earlier.
  • Update the plugin to a patched release once available from the vendor, as noted in the Patchstack advisory.
  • Review existing directory entries for stored payloads and remove any malicious content.
  • Rotate credentials and invalidate active sessions for administrators who accessed affected pages.

Patch Information

At the time of publication, the advisory lists affected versions through 1.34.2. Monitor the plugin repository and the Patchstack advisory for the fixed release. Apply the vendor patch promptly once published.

Workarounds

  • Deactivate and remove the Name Directory plugin until a patched version is installed.
  • Restrict plugin submission capabilities to trusted users only by reviewing WordPress role assignments.
  • Deploy a Content Security Policy (CSP) that disallows inline scripts to reduce exploitation impact.
  • Enable a WordPress-aware WAF to filter XSS payloads targeting plugin endpoints.
bash
# Configuration example: disable the vulnerable plugin via WP-CLI
wp plugin deactivate name-directory
wp plugin delete name-directory

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.