Analysis
Analysis and contextual insights are available on OpenCVE Cloud.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Unknown | WP-Reply Notify | affected |
|
No data.
No data available yet.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
 EUVD |
EUVD-2023-59376 | 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. |
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
|
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 |
|
MITRE
Status: PUBLISHED
Assigner: WPScan
Published:
Updated: 2025-05-20T15:00:41.246Z
Reserved: 2024-01-01T17:34:46.752Z
Link: CVE-2023-7195
Vulnrichment
Updated: 2025-05-20T14:56:53.410Z
NVD
Status : Analyzed
Published: 2025-05-15T20:15:30.293
Modified: 2025-06-11T19:54:14.000
Link: CVE-2023-7195
Redhat
No data.
OpenCVE Enrichment
No data.