Security readout for executives and security teams
Plain-English summary
CVE-2026-3178 affects the WordPress Name Directory plugin. An unauthenticated attacker may store malicious script content through a directory name field, causing it to run for visitors or administrators who view the affected page. The issue is rated high, but the provided sources do not confirm active exploitation.
Executive priority
Prioritize this for WordPress environments using Name Directory, especially public sites with many visitors or privileged administrators. The business risk is account compromise or site manipulation through stored browser-side script execution. Urgency is high, but remediation depends on vendor clarification because only partial patches are identified.
Technical view
Name Directory for WordPress is vulnerable to stored cross-site scripting via the name_directory_name parameter through version 1.32.1. The cause is insufficient input sanitization and output escaping, mapped to CWE-79. The record says versions 1.30.3 and 1.32.1 only partially patched the issue, so a complete fixed version is not identified in the bundle.
Likely exposure
Exposure is likely for public WordPress sites running Name Directory versions up to and including 1.32.1. Sites not using this plugin are not affected based on the provided sources. Administrative users viewing injected pages may face higher business impact.
Exploitation context
The CVSS vector indicates network access, low complexity, and no authentication required. The attack stores script content that later executes when an injected page is viewed. The CVE is not listed as KEV, and the supplied sources do not state active exploitation.
Researcher notes
The source bundle has incomplete affected-version metadata, but the description and Wordfence reference identify Name Directory through 1.32.1. The referenced WordPress Trac files and changeset are useful for reviewing sanitization and escaping changes. Do not assume a complete fix unless confirmed by vendor guidance.
Mitigation direction
- Inventory WordPress sites for the Name Directory plugin and its installed version.
- If version is 1.32.1 or older, treat the site as exposed.
- Check the plugin vendor and WordPress.org page for a fully fixed release or guidance.
- Disable or remove the plugin where it is not business-critical.
- Apply compensating controls for XSS detection until vendor guidance is clear.
Validation and detection
- Confirm whether Name Directory is installed on each WordPress site.
- Record the plugin version and compare it to 1.32.1.
- Review affected directory content for unexpected script-like entries.
- Check Wordfence and the CVE record for updated remediation status.
- Verify any future vendor fix addresses sanitization and output escaping.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-3178 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/3ebac8bc-1dca-4bcd-a033-fb8ed210bf4e?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/name-directory/trunk/admin.php#L931CVE reference
- https://plugins.trac.wordpress.org/browser/name-directory/trunk/helpers.php#L602CVE reference
- https://plugins.trac.wordpress.org/changeset/3478625CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.