# CVE-2024-13826: Email Keep <= 1.1 - Email Deletion via CSRF

> Attackers can force logged-in admins to change Email Keep plugin settings via CSRF, potentially altering email deletion behavior.

- **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:** 8 Mar 2025
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-h337-24ff-jhf6

## What is CVE-2024-13826?

CVE-2024-13826 is a medium-severity vulnerability in Unknown Email Keep, published on 8 Mar 2025. 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 Email Keep WordPress plugin through 1.1 does not have CSRF check in place when updating 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-2024-13826?

It affects 1 product.


Products: Intricateweb Email Keep.

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

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

## Is CVE-2024-13826 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13826 exists.

## Other vulnerabilities in Unknown Email Keep

- [CVE-2024-13825](https://insights.sbomify.com/CVE-2024-13825/): Email Keep <= 1.1 - Reflected XSS (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13826 is a medium-severity vulnerability in Unknown Email Keep, published on 8 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-13826 exists.

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

## Sources

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

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