# CVE-2024-4218: AffiEasy <= 1.1.6 - Cross-Site Request Forgery to Various Actions

> Unauthenticated attackers can trick administrators into performing actions via forged requests due to improper plugin release handling.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2024
- **Updated:** 8 Apr 2026

## What is CVE-2024-4218?

CVE-2024-4218 is a medium-severity vulnerability in perrinalexandre05 AffiEasy, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AffiEasy plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.6. This is due to plugin improperly releasing the tagged and patched version of the plugin - the vulnerable version is used as the core files, while the patched version was included in a 'trunk' folder. This makes it possible for unauthenticated attackers to perform a variety of actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

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


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

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

## Is CVE-2024-4218 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-4218 is a medium-severity vulnerability in perrinalexandre05 AffiEasy, published on 30 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4218 in the wild and no public exploit code.

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

## Sources

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

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