# CVE-2022-2071: Name Directory < 1.25.4 - Stored Cross-Site Scripting via CSRF

> Attackers can inject malicious scripts via CSRF in the Name Directory plugin, potentially compromising admin accounts.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w657-gq68-34f2

## What is CVE-2022-2071?

CVE-2022-2071 is a medium-severity cross-site scripting vulnerability in Unknown Name Directory, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-2071?

It affects 1 product.


Products: Name Directory Project Name Directory.

## How do I fix CVE-2022-2071?

No fix has been published for CVE-2022-2071 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-2071 being exploited?

There is no known exploitation of CVE-2022-2071 in the wild and no public exploit code.

## Other vulnerabilities in Unknown Name Directory

- [CVE-2021-20652](https://insights.sbomify.com/CVE-2021-20652/): Cross-site request forgery in Name Directory (high 8.8)
- [CVE-2022-2072](https://insights.sbomify.com/CVE-2022-2072/): Name Directory < 1.25.3 - Reflected Cross-Site Scripting (medium 6.1)
- [CVE-2023-22692](https://insights.sbomify.com/CVE-2023-22692/): WordPress Name Directory Plugin <= 1.27.1 is vulnerable to Cross Site Request Forgery (CSRF) (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2071 and fix it if it is affected.

What it is: CVE-2022-2071 is a medium-severity cross-site scripting vulnerability in Unknown Name Directory, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-2071 in the wild and no public exploit code.

Affected product: Unknown Name Directory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2071/ (Markdown: https://insights.sbomify.com/CVE-2022-2071/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2071
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2071
- OSV: https://osv.dev/vulnerability/CVE-2022-2071

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2071/
Summaries are generated and may contain mistakes; the official description above is the record.