Is Name Directory safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (1.34.3). As of 2026-11-04. 12 issues are on record for older versions; version 1.34.3 or newer fixes all of them that state a fix. Keep Name Directory on the latest version (1.34.3) and remove it if you do not use it.

Which versions of Name Directory are vulnerable?

Known issues on record (newest first): Stored cross-site scripting (XSS) (1.34.2 and older, fixed in 1.34.3); Missing authorization check (1.34.2 and older, fixed in 1.34.3); Stored cross-site scripting (XSS) (1.32.1 and older, fixed in 1.33.0); Stored cross-site scripting (XSS) (1.32.0 and older, fixed in 1.32.1); Stored cross-site scripting (XSS) (1.30.3 and older, fixed in 1.31.0); Missing authorization check (1.30.0 and older, fixed in 1.30.1). The full list with sources is on this page.

What is the latest version of Name Directory?

1.34.3, according to wordpress.org (last updated 2026-11-04). It has 2,000+ active installs.

What should I do if my Name Directory is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update name-directory). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · name-directory · data as of 2026-11-04

Is Name Directory safe? Known vulnerabilities and latest version

Latest version: 1.34.3
Last updated: 2026-11-04
Active installs: 2,000+
Known issues on record: 12
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 5.3+

Name directory (glossary) with many options like multiple directories, integrated search, non-latin characters, recaptcha, HTML editor and many more. — by Jeroen Peters

What to do

Update to the latest version (1.34.3). Anything older than 1.34.3 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get name-directory --field=version shows what you run; wp plugin update name-directory updates it.

Check your version

Known vulnerabilities

12 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.4 CVE-2026-104726 · published 2026-10-16

Stored cross-site scripting (XSS) in Name Directory (1.34.2 and older)

Affected: 1.34.2 and older
Fixed in: 1.34.3 *
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'dir' Shortcode Attribute in all versions up to, and including, 1.34.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2026-104726 Wordfence advisory Code change (fix)Plugin source

medium 6.5 CVE-2026-104396 · published 2026-10-05

Stored cross-site scripting (XSS) in Name Directory (1.34.2 and older)

Affected: 1.34.2 and older
Fixed in: 1.34.3
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2026-104396 Patchstack advisory

medium 5.3 CVE-2026-104397 · published 2026-10-05

Missing authorization check in Name Directory (1.34.2 and older)

Affected: 1.34.2 and older
Fixed in: 1.34.3
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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.

NVD CVE-2026-104397 Patchstack advisory

high 7.2 CVE-2026-3178 · published 2026-03-11

Stored cross-site scripting (XSS) in Name Directory (1.32.1 and older)

Affected: 1.32.1 and older
Fixed in: 1.33.0 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-3178 Wordfence advisory Code change (fix)Plugin source

high 7.2 CVE-2026-1866 · published 2026-02-10

Stored cross-site scripting (XSS) in Name Directory (1.32.0 and older)

Affected: 1.32.0 and older
Fixed in: 1.32.1 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-1866 Wordfence advisory Code change (fix)Plugin source

high 7.2 CVE-2025-15283 · published 2026-01-14

Stored cross-site scripting (XSS) in Name Directory (1.30.3 and older)

Affected: 1.30.3 and older
Fixed in: 1.31.0 *
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-15283 Wordfence advisory Code change (fix)Plugin source

medium 4.3 CVE-2025-39454 · published 2025-05-19

Missing authorization check in Name Directory (1.30.0 and older)

Affected: 1.30.0 and older
Fixed in: 1.30.1
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in Jeroen Peters Name Directory name-directory.This issue affects Name Directory: from n/a through <= 1.30.0.

NVD CVE-2025-39454 Patchstack advisory

medium 6.5 CVE-2024-43938 · published 2024-09-17

Cross-site scripting (XSS) in Name Directory (1.29.0 and older)

Affected: 1.29.0 and older
Fixed in: 1.29.1
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Jeroen Peters Name Directory name-directory.This issue affects Name Directory: from n/a through <= 1.29.0.

NVD CVE-2024-43938 Patchstack advisory

high 8.8 CVE-2023-22692 · published 2023-05-22

Cross-site request forgery (CSRF) in Name Directory (1.27.1 and older)

Affected: 1.27.1 and older
Fixed in: 1.27.2
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin <= 1.27.1 versions.

NVD CVE-2023-22692 Patchstack advisory

medium 6.1 CVE-2022-2071 · published 2022-07-25

Cross-site request forgery (CSRF) in Name Directory (older than 1.25.4)

Affected: older than 1.25.4
Fixed in: 1.25.4
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

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.

NVD CVE-2022-2071 WPScan advisory

medium 6.1 CVE-2022-2072 · published 2022-07-25

Stored cross-site scripting (XSS) in Name Directory (older than 1.25.3)

Affected: older than 1.25.3
Fixed in: 1.25.3
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

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

NVD CVE-2022-2072 WPScan advisory

high 8.8 CVE-2021-20652 · published 2021-02-05

Cross-site request forgery (CSRF) in Name Directory (1.17.4 and older)

Affected: 1.17.4 and older
Fixed in: 1.18 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

Cross-site request forgery (CSRF) vulnerability in Name Directory 1.17.4 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.

NVD CVE-2021-20652 wordpress.org jvn.jp

Recent activity

2026-11-04 — latest release on wordpress.org (1.34.3).
2026-10-16 — Stored cross-site scripting (XSS) disclosed (CVE-2026-104726), fixed in 1.34.3.
2026-10-05 — Stored cross-site scripting (XSS) disclosed (CVE-2026-104396), fixed in 1.34.3.
2026-10-05 — Missing authorization check disclosed (CVE-2026-104397), fixed in 1.34.3.

Free. We check the CVE feeds every day and email you only when a new issue for Name Directory (name-directory) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (7) · Cross-site request forgery (CSRF) (3) · Missing authorization (2)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/name-directory (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/name-directory"><img src="https://laskyr.com/plugins/name-directory/badge.svg" alt="Name Directory vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Name Directory safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (1.34.3)

What to do

Check your version

Known vulnerabilities

Stored cross-site scripting (XSS) in Name Directory (1.34.2 and older)

Stored cross-site scripting (XSS) in Name Directory (1.34.2 and older)

Missing authorization check in Name Directory (1.34.2 and older)

Stored cross-site scripting (XSS) in Name Directory (1.32.1 and older)

Stored cross-site scripting (XSS) in Name Directory (1.32.0 and older)

Stored cross-site scripting (XSS) in Name Directory (1.30.3 and older)

Missing authorization check in Name Directory (1.30.0 and older)

Cross-site scripting (XSS) in Name Directory (1.29.0 and older)

Cross-site request forgery (CSRF) in Name Directory (1.27.1 and older)

Cross-site request forgery (CSRF) in Name Directory (older than 1.25.4)

Stored cross-site scripting (XSS) in Name Directory (older than 1.25.3)

Cross-site request forgery (CSRF) in Name Directory (1.17.4 and older)

Recent activity

Get an email when Name Directory has a new vulnerability

Browse vulnerabilities

Where this data comes from