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.
History

Wed, 11 Jun 2025 20:15:00 +0000

Type Values Removed Values Added
First Time appeared Ani2life
Ani2life wp-reply Notify
Weaknesses CWE-352
CPEs cpe:2.3:a:ani2life:wp-reply_notify:*:*:*:*:*:wordpress:*:*
Vendors & Products Ani2life
Ani2life wp-reply Notify

Tue, 20 May 2025 15:15:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 15 May 2025 20:15:00 +0000

Type Values Removed Values Added
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.
Title WP-Reply Notify <= 1.1 - Settings Update via CSRF
References

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published: 2025-05-15T20:09:24.545Z

Updated: 2025-05-20T15:00:41.246Z

Reserved: 2024-01-01T17:34:46.752Z

Link: CVE-2023-7195

cve-icon Vulnrichment

Updated: 2025-05-20T14:56:53.410Z

cve-icon NVD

Status : Analyzed

Published: 2025-05-15T20:15:30.293

Modified: 2025-06-11T19:54:14.000

Link: CVE-2023-7195

cve-icon Redhat

No data.