CVE-2022-2072: The Name Directory WordPress plugin before 1.25.3 does not sanitise and escape a parameter before outputting i

Q: How do I fix CVE-2022-2072?

name directory: upgrade to 1.25.3. Exact commands for each OS are on this page.

Q: Is CVE-2022-2072 being exploited?

CVE-2022-2072 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2072 affect?

CVE-2022-2072 affects name directory. Severity is medium (CVSS 6.1). 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

Q: How urgent is CVE-2022-2072?

Priority 40/100. Public exploit reference

This month

MEDIUM 6.1UPGRADE

CVE-2022-2072 is a medium-severity flaw (CVSS 6.1) affecting name directory. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-79
Published	2022-07-25
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: name directory project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-07-25 13:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

name directory project name directory UPGRADE

Affected: < 1.25.3

Fixed in: 1.25.3

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy name-directory || rpm -q name-directory || name-directory --version

2. UPGRADE to 1.25.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade name-directory

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade name-directory

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2072?

name directory: upgrade to 1.25.3. Exact commands for each OS are on this page.

Is CVE-2022-2072 being exploited?

CVE-2022-2072 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2072 affect?

CVE-2022-2072 affects name directory. Severity is medium (CVSS 6.1). 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

How urgent is CVE-2022-2072?

Priority 40/100. Public exploit reference

Software pages

WordPress vulnerabilities

Related CVEs

CVE-2023-22692 MEDIUM 4.3 UPGRADE Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin <= 1.27.1 versions.
CVE-2022-2071 MEDIUM 6.1 UPGRADE The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also l

References

← Back to latest CVEs