{"id":"CVE-2024-13826","aliases":["EUVD-2024-54180","GHSA-h337-24ff-jhf6"],"status":"published","title":"Email Keep \u003c= 1.1 - Email Deletion via CSRF","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","severity":{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","level":"medium","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-11","score":0.00164,"percentile":0.05732,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-352"],"published":"2025-03-08T06:00:06Z","modified":"2026-06-17T07:02:47Z","products":[{"vendor":"intricateweb","product":"email_keep"},{"vendor":"unknown","product":"email keep"}],"references":[{"url":"https://wpscan.com/vulnerability/56b143b6-e5db-4037-ab2a-4e4d0cb7a005/","tags":["exploit","vdb-entry","technical-description","Exploit","Third Party Advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-13826"},{"url":"https://wpscan.com/vulnerability/56b143b6-e5db-4037-ab2a-4e4d0cb7a005"},{"url":"https://github.com/advisories/GHSA-h337-24ff-jhf6"}],"sources":{"cve":[{"id":"CVE-2024-13826","title":"Email Keep \u003c= 1.1 - Email Deletion via CSRF","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","status":"published","published":"2025-03-08T06:00:06.915Z","modified":"2025-03-10T17:22:53.13Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","level":"medium","assessor":"adp"}],"updated_at":"2026-11-02T14:34:13.321108Z"}],"euvd":[{"id":"EUVD-2024-54180","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","status":"published","published":"2025-03-08T06:00:06Z","modified":"2025-03-10T17:22:53Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T20:53:09.715484Z"}],"ghsa":[{"id":"GHSA-h337-24ff-jhf6","title":"The Email Keep WordPress plugin through 1.1 does not have CSRF check in place when updating its...","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","status":"published","published":"2025-03-08T06:30:42Z","modified":"2025-05-06T18:30:36Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","level":"medium"}],"cwes":["CWE-352"],"updated_at":"2026-11-02T15:02:09.053127Z"}],"nvd":[{"id":"CVE-2024-13826","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","status":"published","published":"2025-03-08T06:15:36.657Z","modified":"2026-06-17T07:02:47.933Z","cvss":[{"version":"3.1","score":5.4,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-352"],"updated_at":"2026-11-02T14:10:45.422466Z"}]}}