CSRF in Rename Wp-Login Project
CVE-2022-1732
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
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS: 0.006 (44.2th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 44th percentile — 44.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.005 · newest: 0.006 · change: +0.000
Affected products
- Rename Wp-Login Project
- Rename Wp-Login.php — versions 2.6.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- wpscan.com/vulnerability/3620a087-032e-4a5f-99c8-f9e7e9c29813 (Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2022-1732?
- CVE-2022-1732 is a medium-severity vulnerability in Rename Wp-Login Project, classified under Cross-Site Request Forgery (CSRF). CVSS score: 6.5/10. Published 2022-07-11.
- How severe is CVE-2022-1732?
- Medium severity. CVSS v3 base score is 6.5 out of 10.
- Is CVE-2022-1732 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.