Name Directory
Approved changes feed: RSS · Atom
cpe:2.3:a:jeroenpeters1986:name_directory:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Jeroenpeters1986 (e2343632-e0ce-535d-a704-435bcb5f1fb0) |
|---|---|
| Product | Name Directory (4cd6464f-6c71-536b-a141-4b63a410c20e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-104726 |
vulnerable | 2026-11-03 10:16:19.286871 |
Name Directory <= 1.34.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'dir' Shortcode Attribute
MEDIUM (6.4)
The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'dir' Shortcode Attribute in all versions up to, and including, 1.34.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Published: 2026-10-16T08:27:42.514Z
Updated: 2026-10-16T14:39:01.336Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-3178 |
vulnerable | 2026-06-08 08:01:18.015752 |
Name Directory <= 1.32.1 - Unauthenticated Stored Cross-Site Scripting via 'name_directory_name'
HIGH (7.2)
The Name Directory plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'name_directory_name' parameter in all versions up to, and including, 1.32.1 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. The vulnerability was partially patched in versions 1.30.3 and 1.32.1.
Published: 2026-03-11T11:09:10.516Z
Updated: 2026-04-08T16:47:59.407Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1866 |
vulnerable | 2026-06-08 07:49:09.774597 |
Name Directory <= 1.32.0 - Unauthenticated Stored Cross-Site Scripting via Double HTML-Entity Encoding in Submission Form
HIGH (7.2)
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.
Published: 2026-02-10T09:26:05.323Z
Updated: 2026-04-08T16:43:23.138Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-15283 |
vulnerable | 2026-06-08 07:06:35.987489 |
Name Directory <= 1.30.3 - Unauthenticated Stored Cross-Site Scripting via Multiple Parameters
HIGH (7.2)
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.
Published: 2026-01-14T05:28:07.374Z
Updated: 2026-04-08T16:47:29.731Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.