Name Directory
Approved changes feed: RSS · Atom
cpe:2.3:a:unknown:name_directory:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Unknown (668ca391-a6cc-5e33-879b-83885214de33) |
|---|---|
| Product | Name Directory (30efab1d-00f2-585c-9bda-6c43c2543ff6) |
| 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-2022-2072 |
vulnerable | 2026-06-08 05:42:50.212043 |
Name Directory < 1.25.3 - Reflected Cross-Site Scripting
The Name Directory WordPress plugin before 1.25.3 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting. Furthermore, as the payload is also saved into the database after the request, it leads to a Stored XSS as well
Published: 2022-07-25T12:46:43.000Z
Updated: 2024-08-03T00:24:44.324Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-2071 |
vulnerable | 2026-06-08 05:42:50.210876 |
Name Directory < 1.25.4 - Stored Cross-Site Scripting via CSRF
The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also lacking sanitisation as well as escaping in some of the imported data, which could allow attackers to make a logged in admin import arbitrary names with XSS payloads in them.
Published: 2022-07-25T12:46:28.000Z
Updated: 2024-08-03T00:24:44.139Z |
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.