CVE-2021-24565
The Contact Form 7 Captcha WordPress plugin before 0.0.9 does not have any CSRF check in place when saving its settings, allowing attacker to make a logged in user with the manage_options change them.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.72%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
The Contact Form 7 Captcha WordPress plugin before 0.0.9 does not have any CSRF check in place when saving its settings, allowing attacker to make a logged in user with the manage_options change them. Furthermore, the settings are not escaped when output in attributes, leading to a Stored Cross-Site Scripting issue.
- CVSS 3.1
- 8.8 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 0.72% probability · 52th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-79, CWE-352
- Affected
- contact form 7 captcha project/contact form 7 captcha
- Source
- contact@wpscan.com
References
- https://plugins.trac.wordpress.org/changeset/2570402Patch, Third Party Advisory
- https://wpscan.com/vulnerability/97bfef5e-2ee0-491a-a931-4f44c83e5be0Exploit, Third Party Advisory
- https://plugins.trac.wordpress.org/changeset/2570402Patch, Third Party Advisory
- https://wpscan.com/vulnerability/97bfef5e-2ee0-491a-a931-4f44c83e5be0Exploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.