The Name Directory Project maintains a web-based directory service where its vulnerabilities center on application-layer input handling and request validation, specifically cross-site scripting and cross-site request forgery flaws. Treat this as a compact vendor profile rather than a broad trend line; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Name Directory Project over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2023-22692HIGH Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin <= 1.27.1 versions. | May 22, 2023 | 8.8 | 26 | NO | NO |
CVE-2021-20652HIGH Cross-site request forgery (CSRF) vulnerability in Name Directory 1.17.4 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors. | Feb 5, 2021 | 8.8 | 25 | NO | NO |
CVE-2022-2072MEDIUM 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. Furth | Jul 25, 2022 | 6.1 | 22 | NO | NO |
CVE-2022-2071MEDIUM 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, | Jul 25, 2022 | 6.1 | 22 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Name Directory Project.
Media articles that mention a CVE ID that affects a product developed by Name Directory Project — matched by CVE ID, not by vendor name.