The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when deleting cursors, which could allow attackers to made a logged in admin delete arbitrary cursors via a CSRF attack.
References
Link | Resource |
---|---|
https://wpscan.com/vulnerability/27816c70-58ad-4ffb-adcc-69eb1b210744 | Exploit Third Party Advisory |
https://wpscan.com/vulnerability/27816c70-58ad-4ffb-adcc-69eb1b210744 | Exploit Third Party Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 07:18
Type | Values Removed | Values Added |
---|---|---|
References | () https://wpscan.com/vulnerability/27816c70-58ad-4ffb-adcc-69eb1b210744 - Exploit, Third Party Advisory |
20 Oct 2022, 15:02
Type | Values Removed | Values Added |
---|---|---|
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 4.3 |
References | (CONFIRM) https://wpscan.com/vulnerability/27816c70-58ad-4ffb-adcc-69eb1b210744 - Exploit, Third Party Advisory | |
CPE | cpe:2.3:a:wp_custom_cursors_project:wp_custom_cursors:*:*:*:*:*:wordpress:*:* |
17 Oct 2022, 12:49
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2022-10-17 12:15
Updated : 2024-11-21 07:18
NVD link : CVE-2022-3151
Mitre link : CVE-2022-3151
CVE.ORG link : CVE-2022-3151
JSON object : View
Products Affected
wp_custom_cursors_project
- wp_custom_cursors
CWE
CWE-352
Cross-Site Request Forgery (CSRF)