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-104397 Overview
CVE-2026-104397 is a missing authorization vulnerability in the Jeroen Peters Name Directory plugin for WordPress. The flaw affects all versions up to and including 1.34.2. The plugin fails to enforce access control checks on functionality that permits arbitrary shortcode execution, allowing unauthenticated attackers to invoke shortcodes they should not be able to trigger. The weakness is tracked as CWE-862: Missing Authorization.
Critical Impact
Unauthenticated network attackers can abuse incorrectly configured access control to execute arbitrary shortcodes on affected WordPress sites, leading to limited information disclosure.
Affected Products
- WordPress Name Directory plugin by Jeroen Peters
- All versions from n/a through 1.34.2
- WordPress sites with the vulnerable plugin activated
Discovery Timeline
- 2026-10-05 - CVE-2026-104397 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-104397
Vulnerability Analysis
The Name Directory plugin exposes functionality that processes shortcodes without verifying the caller's authorization state. Because the plugin relies on incorrectly configured access control security levels, requests that should be restricted to privileged roles are accepted from unauthenticated users. An attacker reaching the plugin endpoint over the network can trigger shortcode execution paths intended for authorized contexts.
Shortcode execution in WordPress renders server-side content based on registered handlers. When attacker-controlled input selects which shortcode runs, the attacker effectively borrows the output capability of any installed plugin or theme shortcode. The confidentiality impact is limited to information the invoked shortcode can disclose, with no direct integrity or availability consequences per the published vector.
Root Cause
The root cause is the absence of a capability or nonce check on a shortcode-handling code path. The plugin trusts request parameters to decide whether to render a shortcode, rather than validating the caller through current_user_can() or an equivalent authorization primitive. This matches the CWE-862 pattern of missing authorization on a sensitive action.
Attack Vector
Exploitation is remote and requires no authentication or user interaction. An attacker crafts an HTTP request to the vulnerable plugin endpoint, specifying a shortcode name and attributes. The server renders the shortcode and returns the output. Technical details on the specific request shape are documented in the Patchstack Vulnerability Report. No verified public exploit code is available at the time of publication, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-104397
Indicators of Compromise
- Unauthenticated HTTP requests to Name Directory plugin endpoints under /wp-content/plugins/name-directory/ or admin-ajax actions registered by the plugin
- Request parameters containing shortcode names such as [gallery], [wpconfig], or other registered shortcodes supplied by unauthenticated clients
- Unusual response bodies from the plugin endpoint containing rendered content from unrelated plugins or themes
Detection Strategies
- Review WordPress access logs for POST or GET requests to Name Directory AJAX actions originating from unauthenticated sessions
- Inspect web application firewall telemetry for shortcode-shaped payloads reaching plugin endpoints
- Correlate anomalous shortcode-rendering activity with absent authentication cookies in the same request
Monitoring Recommendations
- Enable verbose logging on the WordPress REST and admin-ajax layers to capture shortcode invocation parameters
- Alert on repeated requests to Name Directory endpoints from a single source IP within short intervals
- Monitor for outbound responses containing data normally restricted to authenticated views
How to Mitigate CVE-2026-104397
Immediate Actions Required
- Identify all WordPress sites running the Name Directory plugin at version 1.34.2 or earlier
- Deactivate the plugin on affected sites until a patched release is installed
- Restrict network access to WordPress administrative endpoints via IP allowlisting where feasible
- Review audit logs for prior exploitation attempts matching the indicators above
Patch Information
At the time of writing, consult the Patchstack Vulnerability Report for the latest fixed version information. Administrators should upgrade to a release later than 1.34.2 once the vendor publishes a corrected build.
Workarounds
- Deactivate the Name Directory plugin until a fixed version is available
- Deploy a web application firewall rule blocking unauthenticated requests to Name Directory plugin endpoints
- Use a WordPress hardening plugin to restrict admin-ajax.php actions registered by the vulnerable plugin to authenticated users
# Example WAF rule concept for blocking unauthenticated shortcode execution
# against the Name Directory plugin endpoint
SecRule REQUEST_URI "@contains /wp-admin/admin-ajax.php" \
"chain,deny,status:403,id:1040397,msg:'Block Name Directory shortcode exec'"
SecRule ARGS:action "@rx ^(nd_|name_directory_)" \
"chain"
SecRule &REQUEST_COOKIES:/wordpress_logged_in_/ "@eq 0"
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

