PatchTheCVECVE-2021-24818: The WP Limits WordPress plugin through 1.0 does not have CSRF check when saving its settings, allowing attacke
CVE-2021-24818 is a medium-severity flaw (CVSS 4.3) affecting wp limits. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP Limits WordPress plugin through 1.0 does not have CSRF check when saving its settings, allowing attacker to make a logged in admin change them, which could make the blog unstable by setting low values
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.4% (top 61%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2021-12-13 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
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-24818?
wp limits: upgrade to newer than 1.0. Exact commands for each OS are on this page.
Is CVE-2021-24818 being exploited?
CVE-2021-24818 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-24818 affect?
CVE-2021-24818 affects wp limits. Severity is medium (CVSS 4.3). The WP Limits WordPress plugin through 1.0 does not have CSRF check when saving its settings, allowing attacker to make a logged in admin change them, which could make the blog unstable by setting low values
How urgent is CVE-2021-24818?
Priority 30/100. Public exploit reference