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)
EPSS: 0.005 (40.6th percentile) — read the EPSS interpretation.
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.
Affected products
- Gopostmatic Replyable
- Unknown Replyable — versions 0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- contact@wpscan.com (Exploit, technical-description, Third Party Advisory, exploit, vdb-entry)
Frequently asked questions
- What is CVE-2022-4265?
- CVE-2022-4265 is a high-severity vulnerability in Gopostmatic Replyable, classified under Cross-Site Request Forgery (CSRF). CVSS score: 8.8/10. Published 2023-03-06.
- How severe is CVE-2022-4265?
- High severity. CVSS v3 base score is 8.8 out of 10.
- Is CVE-2022-4265 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.