CVE-2022-1732: The Rename wp-login.php WordPress plugin through 2.6.0 does not have CSRF check in place when updating the sec

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

rename wp-login: upgrade to newer than 2.6.0. Exact commands for each OS are on this page.

Q: Is CVE-2022-1732 being exploited?

CVE-2022-1732 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-1732 affect?

CVE-2022-1732 affects rename wp-login. Severity is medium (CVSS 6.5). The Rename wp-login.php WordPress plugin through 2.6.0 does not have CSRF check in place when updating the secret login URL, which could allow attackers to make a logged in admin change them via a CSRF attack

Q: How urgent is CVE-2022-1732?

Priority 39/100. Public exploit reference

Routine

MEDIUM 6.5UPGRADE

CVE-2022-1732 is a medium-severity flaw (CVSS 6.5) affecting rename wp-login. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Rename wp-login.php WordPress plugin through 2.6.0 does not have CSRF check in place when updating the secret login URL, which could allow attackers to make a logged in admin change them via a CSRF attack

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-352
Published	2022-07-11
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: rename wp-login 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-11 13:15 UTCPublished CVE record published
2026-06-17 04:23 UTCUpdated Record last modified

rename wp-login project rename wp-login UPGRADE

Affected: <= 2.6.0

Fixed in: newer than 2.6.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy rename-wp-login || rpm -q rename-wp-login || rename-wp-login --version

2. UPGRADE to newer than 2.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rename-wp-login

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rename-wp-login

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-1732?

rename wp-login: upgrade to newer than 2.6.0. Exact commands for each OS are on this page.

Is CVE-2022-1732 being exploited?

CVE-2022-1732 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-1732 affect?

CVE-2022-1732 affects rename wp-login. Severity is medium (CVSS 6.5). The Rename wp-login.php WordPress plugin through 2.6.0 does not have CSRF check in place when updating the secret login URL, which could allow attackers to make a logged in admin change them via a CSRF attack

How urgent is CVE-2022-1732?

Priority 39/100. Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs