# CVE-2024-3971: Similarity <= 3.0 - Plugin Reset via CSRF

> Attackers can force logged-in admins to reset Similarity plugin settings via CSRF, potentially disrupting site configuration.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jun 2024
- **Updated:** 13 Mar 2025
- **Also known as:** GHSA-73gc-wx3f-276g

## What is CVE-2024-3971?

CVE-2024-3971 is a medium-severity vulnerability in Unknown Similarity, published on 14 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Similarity WordPress plugin through 3.0 does not have CSRF check in place when resetting its settings, which could allow attackers to make a logged in admin reset them via a CSRF attack

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

## Which versions are affected by CVE-2024-3971?

It affects 1 product.


Products: Davidjmiller Similarity.

## How do I fix CVE-2024-3971?

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

## Is CVE-2024-3971 being exploited?

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

## Other vulnerabilities in Unknown Similarity

- [CVE-2024-3972](https://insights.sbomify.com/CVE-2024-3972/): Similarity <= 3.0 - Stored XSS via CSRF (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-3971 and fix it if it is affected.

What it is: CVE-2024-3971 is a medium-severity vulnerability in Unknown Similarity, published on 14 Jun 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-3971 in the wild and no public exploit code.

Affected product: Unknown Similarity. 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-2024-3971/ (Markdown: https://insights.sbomify.com/CVE-2024-3971/index.md)
```

## Sources

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

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