WP-Reply Notify <= 1.1 - Settings Update via CSRF
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.
| 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.212% probability within 30 days)
| 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 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
| 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 |
|