CSRF in Givewp

CVE-2022-2260

The GiveWP WordPress plugin before 2.21.3 does not have CSRF in place when exporting data, and does not validate the exporting parameters such as dates, which could allow attackers to make a logged in admin DoS the web server via a CSRF attack as the plugin will try to retrieve data from the database many times which leads to overwhelm the target's CPU.

Vulnerability class: CSRF (Cross-Site Request Forgery)

Published · last modified .

CVSS v3 metric

CVSS v3 base score 6.5 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

EPSS exploit prediction

EPSS: 0.004 (36.3th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 36th percentile — 36.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2022-2260: held from 0.004 to 0.004.

EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: +0.000

Affected products

  • Givewp
  • Givewp – Donation Plugin And Fundraising Platform — versions 2.21.3

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2022-2260?
CVE-2022-2260 is a medium-severity vulnerability in Givewp, classified under Cross-Site Request Forgery (CSRF). CVSS score: 6.5/10. Published 2022-08-01.
How severe is CVE-2022-2260?
Medium severity. CVSS v3 base score is 6.5 out of 10.
Is CVE-2022-2260 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.