{"id":"CVE-2023-7195","aliases":["EUVD-2023-59376","GHSA-rcp3-h3cv-rfv7"],"status":"published","title":"WP-Reply Notify \u003c= 1.1 - Settings Update via CSRF","description":"The WP-Reply Notify WordPress plugin through 1.1 does not have a 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":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"medium","assessor":"adp","from":"cve"},"epss":{"day":"2026-11-11","score":0.00208,"percentile":0.11017,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-352"],"published":"2025-05-15T20:09:24Z","modified":"2026-06-17T06:52:17Z","products":[{"vendor":"ani2life","product":"wp-reply_notify"},{"vendor":"unknown","product":"wp-reply notify"}],"references":[{"url":"https://wpscan.com/vulnerability/72279ca0-6365-4c83-adca-4d8e5808a8c5/","tags":["exploit","vdb-entry","technical-description","Exploit","Third Party Advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-7195"},{"url":"https://wpscan.com/vulnerability/72279ca0-6365-4c83-adca-4d8e5808a8c5"},{"url":"https://github.com/advisories/GHSA-rcp3-h3cv-rfv7"}],"sources":{"cve":[{"id":"CVE-2023-7195","title":"WP-Reply Notify \u003c= 1.1 - Settings Update via CSRF","description":"The WP-Reply Notify WordPress plugin through 1.1 does not have a 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-05-15T20:09:24.545Z","modified":"2025-05-20T15:00:41.246Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"medium","assessor":"adp"}],"updated_at":"2026-11-02T14:35:34.170609Z"}],"euvd":[{"id":"EUVD-2023-59376","description":"The WP-Reply Notify WordPress plugin through 1.1 does not have a 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-05-15T20:09:24Z","modified":"2025-05-20T15:00:41Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T20:32:43.363755Z"}],"ghsa":[{"id":"GHSA-rcp3-h3cv-rfv7","title":"The WP-Reply Notify WordPress plugin through 1.1 does not have a CSRF check in place when...","description":"The WP-Reply Notify WordPress plugin through 1.1 does not have a 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-05-15T21:31:27Z","modified":"2025-06-11T21:30:40Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"medium"}],"cwes":["CWE-352"],"updated_at":"2026-11-02T15:02:42.160981Z"}],"nvd":[{"id":"CVE-2023-7195","description":"The WP-Reply Notify WordPress plugin through 1.1 does not have a 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-05-15T20:15:30.293Z","modified":"2026-06-17T06:52:17.31Z","cvss":[{"version":"3.1","score":4.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-352"],"updated_at":"2026-11-02T14:09:21.774456Z"}]}}