CVE-2025-15283
Unknown Unknown - Not Provided

Stored XSS in WordPress Name Directory Plugin Allows Script Injection

Vulnerability report for CVE-2025-15283, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-01-14

Last updated on: 2026-04-08

Assigner: Wordfence

Description

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 possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-01-14
Last Modified
2026-04-08
Generated
2026-07-06
AI Q&A
2026-01-14
EPSS Evaluated
2026-07-05
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
unknown_vendor name_directory to 1.30.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2025-15283 is a Stored Cross-Site Scripting (XSS) vulnerability in the Name Directory WordPress plugin (up to version 1.30.3). It occurs because the plugin does not properly sanitize and escape user input in the 'name_directory_name' and 'name_directory_description' parameters. This allows unauthenticated attackers to inject malicious scripts that execute whenever a user views a page containing the injected content. The vulnerability stems from insufficient input validation and output escaping in the plugin's handling of submitted names and descriptions. [2]

Impact Analysis

This vulnerability can impact you by allowing attackers to inject arbitrary malicious scripts into pages displayed by the Name Directory plugin. When other users access these pages, the malicious scripts execute in their browsers, potentially leading to theft of user credentials, session hijacking, defacement, or distribution of malware. Since the vulnerability is exploitable by unauthenticated attackers, it poses a significant risk to site visitors and administrators, potentially compromising site security and user trust. [2]

Detection Guidance

Detection of this vulnerability involves identifying if the Name Directory WordPress plugin version 1.30.3 or earlier is installed and if the vulnerable parameters ('name_directory_name' and 'name_directory_description') are being exploited. You can scan your WordPress installation for the plugin version. Additionally, monitoring HTTP requests for suspicious input in these parameters that include script tags or unusual payloads may help detect exploitation attempts. Example commands to check the plugin version on the server (assuming shell access): 1. Navigate to the WordPress plugins directory and check the plugin version file: `grep 'Version' wp-content/plugins/name-directory/readme.txt` or `grep 'Version' wp-content/plugins/name-directory/name-directory.php` 2. Use curl or wget to test for XSS by submitting payloads to the form handling these parameters and observing if scripts execute or are reflected unsanitized. Example curl command to test injection: `curl -X POST -d "name_directory_name=<script>alert(1)</script>&name_directory_description=test" https://yourwordpresssite.com/path-to-name-directory-form` Monitoring web server logs for such payloads can also help detect attempts. However, no specific detection commands are provided in the resources. [2]

Mitigation Strategies

Immediate mitigation steps include: 1. Update the Name Directory plugin to a version later than 1.30.3 where the vulnerability is fixed. 2. If an update is not immediately available, consider disabling or removing the plugin to prevent exploitation. 3. Implement Web Application Firewall (WAF) rules to block requests containing suspicious script tags or payloads targeting the 'name_directory_name' and 'name_directory_description' parameters. 4. Review and strengthen input sanitization and output escaping in the plugin code if you maintain a custom version. 5. Ensure that WordPress and all plugins are kept up to date and monitor for security patches. 6. Consider restricting access to the plugin's submission forms or enabling admin approval for submissions to reduce risk. These steps help prevent unauthenticated attackers from injecting malicious scripts via the vulnerable parameters. [2, 3]

Compliance Impact

The provided resources do not contain information regarding the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-15283. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart