CVE-2024-13836: The WP Login Control WordPress plugin through 2.0.0 does not sanitise and escape a parameter before outputting

Q: How do I fix CVE-2024-13836?

wp login control: upgrade to newer than 2.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2024-13836 being exploited?

CVE-2024-13836 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-2024-13836 affect?

CVE-2024-13836 affects wp login control. Severity is high (CVSS 7.1). The WP Login Control WordPress plugin through 2.0.0 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

Q: How urgent is CVE-2024-13836?

Priority 35/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2024-13836 is a high-severity flaw (CVSS 7.1) affecting wp login control. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Login Control WordPress plugin through 2.0.0 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-79
Published	2025-03-11
Last modified	2026-06-17

Publisher (CNA): WPScan · Vendor: forsyspress

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

Am I affected?

Timeline

2025-03-11 06:15 UTCPublished CVE record published
2026-06-17 07:02 UTCUpdated Record last modified

forsyspress wp login control UPGRADE

Affected: <= 2.0.0

Fixed in: newer than 2.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-login-control

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-2024-13836?

wp login control: upgrade to newer than 2.0.0. Exact commands for each OS are on this page.

Is CVE-2024-13836 being exploited?

CVE-2024-13836 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-2024-13836 affect?

CVE-2024-13836 affects wp login control. Severity is high (CVSS 7.1). The WP Login Control WordPress plugin through 2.0.0 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin.

How urgent is CVE-2024-13836?

Priority 35/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs