CVE-2026-1866: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in jeroenpeters1986 Name Directory
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.
AI Analysis
Technical Summary
CVE-2026-1866 is a stored XSS vulnerability in the Name Directory plugin for WordPress caused by the plugin's sanitization function calling html_entity_decode() before wp_kses(), and again on output. This double decoding bypasses sanitization, enabling injection of arbitrary web scripts through public submission form parameters. The vulnerability affects all versions up to and including 1.32.0. Attackers do not require authentication but need administrative approval or auto-publish to trigger script execution in users' browsers.
Potential Impact
Successful exploitation allows attackers to execute arbitrary scripts in the context of users visiting the affected pages, potentially leading to session hijacking, defacement, or other client-side attacks. The vulnerability has a CVSS 3.1 score of 7.2 (high severity) with network attack vector, low attack complexity, no privileges or user interaction required, and impacts confidentiality and integrity with no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should disable public submissions or require manual review and approval of all submissions to prevent untrusted input from being published. Monitoring for suspicious submissions and applying web application firewall rules to detect XSS payloads may provide temporary mitigation.
CVE-2026-1866: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in jeroenpeters1986 Name Directory
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-1866 is a stored XSS vulnerability in the Name Directory plugin for WordPress caused by the plugin's sanitization function calling html_entity_decode() before wp_kses(), and again on output. This double decoding bypasses sanitization, enabling injection of arbitrary web scripts through public submission form parameters. The vulnerability affects all versions up to and including 1.32.0. Attackers do not require authentication but need administrative approval or auto-publish to trigger script execution in users' browsers.
Potential Impact
Successful exploitation allows attackers to execute arbitrary scripts in the context of users visiting the affected pages, potentially leading to session hijacking, defacement, or other client-side attacks. The vulnerability has a CVSS 3.1 score of 7.2 (high severity) with network attack vector, low attack complexity, no privileges or user interaction required, and impacts confidentiality and integrity with no availability impact.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should disable public submissions or require manual review and approval of all submissions to prevent untrusted input from being published. Monitoring for suspicious submissions and applying web application firewall rules to detect XSS payloads may provide temporary mitigation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-02-03T21:37:47.348Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 698afe6e4b57a58fa1f900fe
Added to database: 2/10/2026, 9:46:22 AM
Last enriched: 4/9/2026, 10:01:25 PM
Last updated: 5/22/2026, 1:10:26 PM
Views: 99
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.