CSRF in Gopostmatic Replyable
CVE-2022-4265
The Replyable WordPress plugin before 2.2.10 does not validate the class name submitted by the request when instantiating an object in the prompt_dismiss_notice action and also lacks CSRF check in the related action. This could allow any authenticated users, such as subscriber to perform Object Injection attacks. The attack could also be done via a CSRF vector against any authenticated user
Vulnerability class: CSRF (Cross-Site Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.005, 44.1th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Gopostmatic Replyable
- Replyable — versions 0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (20142995/nuclei-templates). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- wpscan.com/vulnerability/095cba08-7edd-41fb-9776-da151c0885dd (Exploit, technical-description, Third Party Advisory, exploit, vdb-entry)