# CVE-2021-24776: WP Performance Score Booster < 2.1 - Settings Change via CSRF


- **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
- **Fix available:** No
- **Published:** 17 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-92wq-xf5r-xg8f

## What is CVE-2021-24776?

CVE-2021-24776 is a medium-severity vulnerability in Unknown WP Performance Score Booster – Optimize Speed, Enable Cache & Page Preload, published on 17 Nov 2021. 

### Official description

The WP Performance Score Booster WordPress plugin before 2.1 does not have CSRF check when saving its settings, which could allow attackers to make a logged in admin change them via a CSRF attack.

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

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

It affects 1 product.


Products: Wp Performance Score Booster Project Wp Performance Score Booster.

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

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

## Is CVE-2021-24776 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24776 is a medium-severity vulnerability in Unknown WP Performance Score Booster – Optimize Speed, Enable Cache & Page Preload, published on 17 Nov 2021. 
Exploitation: There is no known exploitation of CVE-2021-24776 in the wild and no public exploit code.

Affected product: Unknown WP Performance Score Booster – Optimize Speed, Enable Cache & Page Preload. 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-24776/ (Markdown: https://insights.sbomify.com/CVE-2021-24776/index.md)
```

## Sources

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

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