CVE-2022-3149

The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editing cursors, which could allow attackers to made a logged in admin perform such actions via CSRF attacks. Furthermore, due to the lack of sanitisation and escaping in some of the cursor options, it could also lead to Stored Cross-Site Scripting

CVSS v3 6.1 MEDIUM

6.1^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 2.8 / Impact : 2.7

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction REQUIRED

Confidentiality Impact LOW

Integrity Impact LOW

Availability Impact NONE

Scope CHANGED

References

Link	Resource
https://wpscan.com/vulnerability/4c13a93d-2100-4721-8937-a1205378655f	Exploit Third Party Advisory
https://wpscan.com/vulnerability/4c13a93d-2100-4721-8937-a1205378655f	Exploit Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:wp_custom_cursors_project:wp_custom_cursors:*:*:*:*:*:wordpress:*:*

History

21 Nov 2024, 07:18

Type	Values Removed	Values Added
References	~~() https://wpscan.com/vulnerability/4c13a93d-2100-4721-8937-a1205378655f - Exploit, Third Party Advisory~~	() https://wpscan.com/vulnerability/4c13a93d-2100-4721-8937-a1205378655f - Exploit, Third Party Advisory

Information

Published : 2022-10-17 12:15

Updated : 2024-11-21 07:18

NVD link : CVE-2022-3149

Mitre link : CVE-2022-3149

CVE.ORG link : CVE-2022-3149

JSON object : View

Products Affected

wp_custom_cursors_project

wp_custom_cursors

CWE

CWE-79

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

CWE-352

Cross-Site Request Forgery (CSRF)

{"id": "CVE-2022-3149", "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 6.1, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 2.7, "exploitabilityScore": 2.8}]}, "published": "2022-10-17T12:15:10.340", "references": [{"url": "https://wpscan.com/vulnerability/4c13a93d-2100-4721-8937-a1205378655f", "tags": ["Exploit", "Third Party Advisory"], "source": "contact@wpscan.com"}, {"url": "https://wpscan.com/vulnerability/4c13a93d-2100-4721-8937-a1205378655f", "tags": ["Exploit", "Third Party Advisory"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "contact@wpscan.com", "description": [{"lang": "en", "value": "CWE-79"}, {"lang": "en", "value": "CWE-352"}]}], "descriptions": [{"lang": "en", "value": "The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editing cursors, which could allow attackers to made a logged in admin perform such actions via CSRF attacks. Furthermore, due to the lack of sanitisation and escaping in some of the cursor options, it could also lead to Stored Cross-Site Scripting"}, {"lang": "es", "value": "El plugin WP Custom Cursors de WordPress versiones anteriores a 3.0.1, no presenta una comprobaci\u00f3n de tipo CSRF cuando se crean y editan cursores, lo que podr\u00eda permitir a atacantes hacer que un administrador conectado lleve a cabo dichas acciones por medio de ataques de tipo CSRF. Adem\u00e1s, debido a una falta de saneo y escape en algunas de las opciones del cursor, tambi\u00e9n podr\u00eda conllevar a un ataque de tipo Cross-Site Scripting Almacenado"}], "lastModified": "2024-11-21T07:18:55.770", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:wp_custom_cursors_project:wp_custom_cursors:*:*:*:*:*:wordpress:*:*", "vulnerable": true, "matchCriteriaId": "76D7B555-015B-41EE-B495-5D7E0EB6EDC9", "versionEndExcluding": "3.0.1"}], "operator": "OR"}]}], "sourceIdentifier": "contact@wpscan.com"}