CVE-2021-24536: The Custom Login Redirect WordPress plugin through 1.0.0 does not have CSRF check in place when saving its set

Q: How do I fix CVE-2021-24536?

custom login redirect: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2021-24536 being exploited?

CVE-2021-24536 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-2021-24536 affect?

CVE-2021-24536 affects custom login redirect. Severity is medium (CVSS 6.1). The Custom Login Redirect WordPress plugin through 1.0.0 does not have CSRF check in place when saving its settings, and do not sanitise or escape user input before outputting them back in the page, leading to a Stored Cross-Site Scripting

Q: How urgent is CVE-2021-24536?

Priority 35/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2021-24536 is a medium-severity flaw (CVSS 6.1) affecting custom login redirect. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Custom Login Redirect WordPress plugin through 1.0.0 does not have CSRF check in place when saving its settings, and do not sanitise or escape user input before outputting them back in the page, leading to a Stored Cross-Site Scripting issue

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.4% (top 65%)
CISA exploited list	No
Weakness	CWE-79, CWE-352
Published	2021-08-16
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: custom login redirect project

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

Am I affected?

Timeline

2021-08-16 11:15 UTCPublished CVE record published
2026-06-17 03:40 UTCUpdated Record last modified

custom login redirect project custom login redirect UPGRADE

Affected: <= 1.0.0

Fixed in: newer than 1.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy custom-login-redirect || rpm -q custom-login-redirect || custom-login-redirect --version

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

sudo apt update && sudo apt install --only-upgrade custom-login-redirect

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade custom-login-redirect

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-2021-24536?

custom login redirect: upgrade to newer than 1.0.0. Exact commands for each OS are on this page.

Is CVE-2021-24536 being exploited?

CVE-2021-24536 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-2021-24536 affect?

CVE-2021-24536 affects custom login redirect. Severity is medium (CVSS 6.1). The Custom Login Redirect WordPress plugin through 1.0.0 does not have CSRF check in place when saving its settings, and do not sanitise or escape user input before outputting them back in the page, leading to a Stored Cross-Site Scripting

How urgent is CVE-2021-24536?

Priority 35/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs