Name Directory
name-directory · plugin
Known security vulnerabilities for Name Directory. Find out in seconds which version runs on your site with WP Lens.
7 known vulnerabilities
5 exploitable without logging in · latest Mar 11, 2026
Listed on wordpress.org · latest 1.34.3 · last updated Oct 1, 2026 · 2K+ installs
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 8.8
CVE-2023-22692unauthenticated · needs a click≤ 1.27.1
WordPress Name Directory Plugin <= 1.27.1 is vulnerable to Cross Site Request Forgery (CSRF)
- High 8.8
CVE-2021-20652unauthenticated · needs a click
Cross-site request forgery (CSRF) vulnerability in Name Directory 1.17.4 and earlier allows remote attackers to hijack the authentication of
- High 7.2
CVE-2026-3178unauthenticated≤ 1.32.1
Name Directory <= 1.32.1 - Unauthenticated Stored Cross-Site Scripting via 'name_directory_name'
- High 7.2
CVE-2026-1866unauthenticated≤ 1.32.0
Name Directory <= 1.32.0 - Unauthenticated Stored Cross-Site Scripting via Double HTML-Entity Encoding in Submission Form
- High 7.2
CVE-2025-15283unauthenticated≤ 1.30.3
Name Directory <= 1.30.3 - Unauthenticated Stored Cross-Site Scripting via Multiple Parameters
- Medium 6.5
CVE-2024-43938login required≤ 1.29.0
WordPress Name Directory plugin <= 1.29.0 - Reflected Cross Site Scripting (XSS) vulnerability
- Medium 4.3
CVE-2025-39454login required≤ 1.30.0
WordPress Name Directory plugin <= 1.30.0 - Broken Access Control vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).