# CVE-2021-24674: Genie WP Favicon <= 0.5.2 - Arbitrary Favicon Change via CSRF

> Attackers can force logged-in administrators to change the site favicon via CSRF due to missing token validation in the Genie WP Favicon plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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:** 8 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mhcf-w95r-xjvr

## What is CVE-2021-24674?

CVE-2021-24674 is a medium-severity vulnerability in Unknown Genie WP Favicon, published on 8 Nov 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 Genie WP Favicon WordPress plugin through 0.5.2 does not have CSRF in place when updating the favicon, which could allow attackers to make a logged in admin change it via a CSRF attack

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

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

It affects 1 product.


Products: Genie Wp Favicon Project Genie Wp Favicon.

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

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

## Is CVE-2021-24674 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-24674 is a medium-severity vulnerability in Unknown Genie WP Favicon, published on 8 Nov 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-24674 in the wild and no public exploit code.

Affected product: Unknown Genie WP Favicon. 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-24674/ (Markdown: https://insights.sbomify.com/CVE-2021-24674/index.md)
```

## Sources

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

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