HomeWordPress vulnerabilitiesName Directory
Name Directory vulnerabilities
Name Directory has 7 known vulnerabilities in this database. The most recent published record is dated 5 Oct 2026.
- Known vulnerabilities
- 7
- Active installs
- 2,000+
- Latest version
- 1.34.2
- Last updated
- 19 Sep 2026
- Most recent
- 5 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-104396 | Medium 6.5 | Up to 1.34.2 | No fixed version yet | 2 d ago |
| Broken access control CVE-2026-104397 | Medium 5.3 | Up to 1.34.2 | No fixed version yet | 2 d ago |
| Cross-site scripting (XSS) CVE-2026-3178 | High 7.2 | Up to 1.32.1 | Fixed in a later version (latest 1.34.2) | 11 Mar 2026 |
| Cross-site scripting (XSS) CVE-2026-1866 | High 7.2 | Up to 1.32.0 | Fixed in a later version (latest 1.34.2) | 10 Feb 2026 |
| Cross-site scripting (XSS) CVE-2025-15283 | High 7.2 | Up to 1.30.3 | Fixed in a later version (latest 1.34.2) | 14 Jan 2026 |
| Cross-site scripting (XSS) CVE-2022-2071 | Medium 6.1 | Before 1.25.4 | Fixed in 1.25.4 | 25 Jul 2022 |
| Cross-site scripting (XSS) CVE-2022-2072 | Medium 6.1 | Before 1.25.3 | Fixed in 1.25.3 | 25 Jul 2022 |
Read the published descriptions
- CVE-2026-104396, 5 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jeroen Peters Name Directory name-directory allows Stored XSS.This issue affects Name Directory: from n/a through 1.34.2. CVE record
- CVE-2026-104397, 5 Oct 2026
- Missing Authorization vulnerability in Jeroen Peters Name Directory name-directory allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Name Directory: from n/a through 1.34.2. CVE record
- CVE-2026-3178, 11 Mar 2026
- The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name_directory_name' parameter in all versions up to, and including, 1.32.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability was partially patched in versions 1.30.3 and 1.32.1. CVE record
- CVE-2026-1866, 10 Feb 2026
- The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via double HTML-entity encoding in all versions up to, and including, 1.32.0. This is due to the plugin's sanitization function calling `html_entity_decode()` before `wp_kses()`, and then calling `html_entity_decode()` again on output. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page via the 'name_directory_name' and 'name_directory_description' parameters in the public submission form granted they can trick the site administrator into approving their submission or auto-publish is enabled. CVE record
- CVE-2025-15283, 14 Jan 2026
- The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name_directory_name' and 'name_directory_description' parameters in all versions up to, and including, 1.30.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2022-2071, 25 Jul 2022
- The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also lacking sanitisation as well as escaping in some of the imported data, which could allow attackers to make a logged in admin import arbitrary names with XSS payloads in them. CVE record
- CVE-2022-2072, 25 Jul 2022
- The Name Directory WordPress plugin before 1.25.3 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting. Furthermore, as the payload is also saved into the database after the request, it leads to a Stored XSS as well CVE record
What to do if you run Name Directory
If you run Name Directory, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Name Directory vulnerabilities
Free. We email you when a new vulnerability is published for Name Directory, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.