# CVE-2021-24818: WP Limits <= 1.0 - Plugin's Settings Update via CSRF

> A CSRF vulnerability in the WP Limits WordPress plugin allows attackers to force logged-in admins to modify plugin settings, potentially destabilizing the site.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Dec 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hfgv-8383-5fm8

## What is CVE-2021-24818?

CVE-2021-24818 is a medium-severity vulnerability in Unknown Wp Limits, published on 13 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-24818?

It affects 1 product.


Products: Wp Limits Project Wp Limits.

## How do I fix CVE-2021-24818?

No fix has been published for CVE-2021-24818 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-24818 being exploited?

There is no known exploitation of CVE-2021-24818 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24818 and fix it if it is affected.

What it is: CVE-2021-24818 is a medium-severity vulnerability in Unknown Wp Limits, published on 13 Dec 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-24818 in the wild and no public exploit code.

Affected product: Unknown Wp Limits. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-24818/ (Markdown: https://insights.sbomify.com/CVE-2021-24818/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-24818
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-24818
- OSV: https://osv.dev/vulnerability/CVE-2021-24818

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-24818/
Summaries are generated and may contain mistakes; the official description above is the record.