CSRF in Name Directory Project
CVE-2022-2071
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.
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.1 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N.
EPSS exploit prediction
EPSS: 0.003 (24.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 24th percentile — 24.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.003 · newest: 0.003 · change: +0.000
Affected products
- Name Directory Project
- Name Directory — versions 1.25.4
Weakness classification (CWE)
Public proof-of-concept exploits
References
- wpscan.com/vulnerability/d3653976-9e0a-4f2b-87f7-26b5e7a74b9d (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2022-2071?
- CVE-2022-2071 is a medium-severity vulnerability in Name Directory Project, classified under Cross-Site Request Forgery (CSRF). CVSS score: 6.1/10. Published 2022-07-25.
- How severe is CVE-2022-2071?
- Medium severity. CVSS v3 base score is 6.1 out of 10.
- Is CVE-2022-2071 known to be exploited?
- 4 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.