Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
DeliverySubmit directory entry with XSS payload
-
ExploitPayload stored in plugin data
-
ExecutionAdmin/visitor loads directory page
-
PersistScript executes in victim browser
-
ImpactHijack session or perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated account with at least low privileges that can submit or edit Name Directory entries (PR:L), and the stored payload only fires when a victim - typically an administrator or site visitor - subsequently views the affected directory page (UI:R). Limiting factors: the attacker must already be able to author directory content, the payload is inert until another user loads the page, and impact is confined to browser-context script execution (C:L/I:L/A:L) rather than direct server takeover. Realistic exposure is highest on sites that allow untrusted or multiple contributors to populate directory listings; single-admin sites with no untrusted authenticated users face minimal practical risk. |
| Impact | This is a Patchstack-reported stored XSS (CWE-79) in the Name Directory WordPress plugin with a moderate CVSS 3.1 score of 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L). The vector indicates a network-reachable, low-complexity attack that requires an authenticated low-privilege account (PR:L) and victim interaction (UI:R), with a scope change (S:C) reflecting that injected script executes in other users'/admins' browser context rather than the vulnerable component itself. Impacts are rated Low across confidentiality, integrity, and availability - consistent with typical stored XSS rather than direct server compromise. No EPSS score, KEV listing, or POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the real-world urgency is therefore driven by the vulnerability class and the plugin's footprint, not by observed in-the-wild activity. Net assessment: a genuine but second-tier priority - meaningful where the plugin is deployed and untrusted contributors can submit directory entries, but not an emergency absent exploitation signals. Missing data to note explicitly: EPSS probability is absent (cannot gauge likelihood of widespread exploitation), KEV status is not confirmed, and POC availability is unknown. |
| Exploit ScenarioDerived | A low-privileged authenticated user (e.g., a contributor or a user permitted to submit/edit name-directory entries) injects a malicious script payload into a stored field of the Name Directory plugin. When an administrator or another visitor later views the affected directory page, the stored script executes in their browser session, enabling session/cookie theft or actions performed as the victim. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 05, 2026
Stored cross-site scripting in the WordPress plugin Name Directory (versions through 1.34.2) lets an authenticated attacker with low privileges (PR:L) save a script payload into directory content that executes in the browser of any user who later views the affected page (UI:R). Because the injected content persists, a single submission can fire for administrators or visitors on every subsequent page load, though the attacker must already hold an account able to author or edit Name Directory entries and the payload remains inert until someone else opens the page; per the CVSS vector PR:N is absent, so this is an authenticated-context issue rather than an unauthenticated one. The independent assessment rates it CVSS 3.1 6.5 (AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L), with impact confined to browser-context script execution and no public exploit identified at time of analysis.
RemediationAI
No vendor-released patch is identified in the available data, and no fixed version number is provided, so remediation must begin with compensating controls while monitoring the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/name-directory/vulnerability/wordpress-name-directory-plugin-1-34-2-cross-site-scripting-xss-vulnerability?_s_id=cve) for a released patched version. Where the plugin is not business-critical, deactivating it removes the exposure entirely; the trade-off is loss of the directory functionality. If it must remain active, reduce the attack surface by tightening WordPress roles so that only fully trusted administrators can create or edit Name Directory entries - remove or downgrade Contributor/Author accounts that can submit listings, and enforce moderation so no entry publishes without review, accepting the operational cost of manual approval. Sites that custom-templated the directory views can additionally apply output escaping (esc_html, esc_attr, wp_kses) to the fields that render user-supplied names and details, though this only helps where a custom template is in use rather than the plugin's shipped views. A WAF rule filtering script payloads on the plugin's submission endpoints provides defense in depth but can be bypassed through encoding tricks and should not be the sole control.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-79, improper neutralization of input during web page generation, in a WordPress plugin: user-supplied fields used to build directory listing pages are written to the database and later rendered without adequate output encoding, so markup and script content survive storage and execute in the victim's browser context. The affected CPE, cpe:2.3:a:jeroen_peters:name_directory:*:*:*:*:*:*:*:*, indicates all releases of Jeroen Peters' Name Directory plugin up to and including 1.34.2 are in scope. The CVSS scope change (S:C) reflects that the injected script affects resources beyond the plugin's own origin boundary from the user's perspective, while the low confidentiality, integrity, and availability values (C:L/I:L/A:L) confirm the consequence is script execution in the victim's session rather than server compromise. Because the vector carries PR:L, an attacker must first hold at least a low-privileged account permitted to submit or edit directory entries - the classic WordPress pattern where Contributor/Author-level roles can persist content that an administrator later renders. This is disclosed by Patchstack as a WordPress plugin vulnerability and tagged across WordPress, XSS, WordPress Plugin, and Name Directory categories.
Know when Name Directory gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
Authenticated low-privilege user stores the payload (PR:L), a victim must load the page (UI:R), and script runs cross-context in the victim's browser (S:C) with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
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.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Name Directory
View allThe Name Directory WordPress plugin before 1.25.3 does not sanitise and escape a parameter before outputting it back in
The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also lacking san
Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin <= 1.27.1 versions. Rated high se
Cross-site request forgery (CSRF) vulnerability in Name Directory 1.17.4 and earlier allows remote attackers to hijack t
Stored cross-site scripting in the WordPress Name Directory plugin (all versions up to and including 1.34.2) allows auth
Missing authorization in the WordPress Name Directory plugin (through version 1.34.2) lets remote, unauthenticated attac
EUVD-2026-92324
GHSA-rxxf-9622-7fvg
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB