CVE-2021-24328: The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its setting

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

wp login security and history: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Q: Is CVE-2021-24328 being exploited?

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

CVE-2021-24328 affects wp login security and history. Severity is medium (CVSS 6.2). The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin's set

Q: How urgent is CVE-2021-24328?

Priority 39/100. Public exploit reference

Routine

MEDIUM 6.2UPGRADE

CVE-2021-24328 is a medium-severity flaw (CVSS 6.2) affecting wp login security and history. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin's settings to arbitrary values, and set XSS payloads on them as well

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.2 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	Required
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-352, CWE-79
Published	2021-06-01
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: clogica

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

Am I affected?

Timeline

2021-06-01 14:15 UTCPublished CVE record published
2026-06-17 03:39 UTCUpdated Record last modified

clogica wp login security and history UPGRADE

Affected: <= 1.0

Fixed in: newer than 1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-login-security-and-history || rpm -q wp-login-security-and-history || wp-login-security-and-history --version

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

sudo apt update && sudo apt install --only-upgrade wp-login-security-and-history

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-login-security-and-history

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

wp login security and history: upgrade to newer than 1.0. Exact commands for each OS are on this page.

Is CVE-2021-24328 being exploited?

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

CVE-2021-24328 affects wp login security and history. Severity is medium (CVSS 6.2). The WP Login Security and History WordPress plugin through 1.0 did not have CSRF check when saving its settings, not any sanitisation or validation on them. This could allow attackers to make logged in administrators change the plugin's set

How urgent is CVE-2021-24328?

Priority 39/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs