# CVE-2024-3471: Button Generator < 3.0 - Button Deletion via CSRF


- **Severity:** Low 3.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 May 2024
- **Updated:** 20 Nov 2024
- **Also known as:** GHSA-p6qv-frqj-63r6

## What is CVE-2024-3471?

CVE-2024-3471 is a low-severity vulnerability in Unknown Button Generator , published on 2 May 2024. 

### Official description

The Button Generator  WordPress plugin before 3.0 does not have CSRF check in place when bulk deleting, which could allow attackers to make a logged in admin delete buttons via a CSRF attack

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

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

It affects 1 product.


Products: Wow-Company Button Generator.

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

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

## Is CVE-2024-3471 being exploited?

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

## Other vulnerabilities in Unknown Button Generator 

- [CVE-2021-25052](https://insights.sbomify.com/CVE-2021-25052/): Button Generator < 2.3.3 - RFI leading to RCE via CSRF (high 8.8)
- [CVE-2023-49155](https://insights.sbomify.com/CVE-2023-49155/): WordPress Button Generator – easily Button Builder Plugin <= 2.3.8 is vulnerable to Cross Site Request Forgery (CSRF) (medium 4.3)
- [CVE-2023-25443](https://insights.sbomify.com/CVE-2023-25443/): WordPress Button Generator – easily Button Builder Plugin <= 2.3.5 is vulnerable to Cross Site Request Forgery (CSRF) (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-3471 is a low-severity vulnerability in Unknown Button Generator , published on 2 May 2024. 
Exploitation: There is no known exploitation of CVE-2024-3471 in the wild and no public exploit code.

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

## Sources

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

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