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 con...
Product
wordpress name-directory vulnerabilities
13 published CVES affecting wordpress name-directory, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 13
- Critical
- 0
- High
- 6
- Medium
- 7
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest wordpress name-directory CVEs
Newest publication first
-
MediumCVSS 6.4 EPSS 0.19%
-
CVE-2026-104396 WordPress Name Directory plugin <= 1.34.2 - Cross Site Scripting (XSS) vulnerability
PublishedMediumCVSS 6.5 EPSS 0.16%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.
-
MediumCVSS 5.3 EPSS 0.22%
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.
-
HighCVSS 7.2 EPSS 0.29%
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 attacke...
-
HighCVSS 7.2 EPSS 0.30%
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 htm...
-
HighCVSS 7.2 EPSS 0.36%
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 po...
-
CVE-2025-39454 WordPress Name Directory plugin <= 1.30.0 - Broken Access Control vulnerability
PublishedMediumCVSS 4.3 EPSS 0.25%Missing Authorization vulnerability in Jeroen Peters Name Directory name-directory.This issue affects Name Directory: from n/a through <= 1.30.0.
-
HighCVSS 7.1 EPSS 0.26%
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.
-
HighCVSS 8.8 EPSS 0.27%
Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin <= 1.27.1 versions.
-
MediumCVSS 6.1 EPSS 0.69%
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 a...
-
MediumCVSS 6.1 EPSS 0.34%
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 th...
-
MediumCVSS 6.3
The Name Directory plugin for WordPress is vulnerable to unauthorized settings update due to insufficient permissions checking on the name_directory_options() function in versions up to, and including, 1.25.4. This makes it possible for authenticated attackers with minimal permis...
-
HighCVSS 8.8 EPSS 0.85%
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.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.