Name Directory <= 1.32.0 - Unauthenticated Stored Cross-Site Scripting via Double HTML-Entity Encoding in Submission Form
Strategic Overview
- Status
- Patched in 1.32.1
- Affected Plugin
- Name Directory
- Affected Version
<= 1.32.0- CVSS
- 7.2High
- Weakness type
- CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
- CVE
CVE-2026-1866
At a glance
CVE-2026-1866 is a high-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Name Directory WordPress plugin, affecting versions <= 1.32.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.32.1; sites on affected versions should update now. Disclosed February 2026, reported by duy.thai.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Name Directory <= 1.32.0 carries this weakness at name_directory_name, and reaching it takes no account at all. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.
Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Name Directory the fix is 1.32.1: builds <= 1.32.0 are affected, anything from 1.32.1 onward is not.
Remediation
Update to version 1.32.1, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Name Directory 1.32.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
- 7.2CVE-2026-3178: Name Directory <= 1.32.1 Stored Cross-Site Scripting
CVE-2026-3178 - 7.2CVE-2025-15283: Name Directory <= 1.30.3 Stored Cross-Site Scripting
CVE-2025-15283 - 6.1CVE-2024-43938: Name Directory <= 1.29.0 Reflected XSS
CVE-2024-43938 - 6.1CVE-2022-2072: Name Directory <= 1.25.2 Cross-Site Scripting
CVE-2022-2072
Other vulnerabilities in Name Directory
- 8.8CVE-2022-2071: Name Directory <= 1.25.3 Cross-Site Request Forgery
CVE-2022-2071 - 8.8CVE-2021-20652: Name Directory <= 1.17.4 Cross-Site Request Forgery
CVE-2021-20652 - 6.3Name Directory <= 1.25.4 Unauthorized Settings Update
- 4.3CVE-2025-39454: Name Directory <= 1.30.0 Missing Authorization
CVE-2025-39454 - 4.3CVE-2023-22692: Name Directory <= 1.27.1 Cross Site Request Forgery
CVE-2023-22692
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C