Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2022-2260

CVE-2022-2260 - Before 2 Plugin

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.

CVE-2022-2260

MEDIUM CVSS 6.5 Published 2022-08-01 Updated 2024-11-21
AI Risk Elevated (56/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority
Severity Band MEDIUM
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Affected Components 2
Reference Links 1
AI Risk Engine Elevated (56/100)
Exploitability Medium
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2022-08-01 CVE published and first recorded in the threat feed.
  2. 2024-11-21 Record updated with latest vulnerability metadata.
  3. 2026-04-10 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 5 days ago

AI enriched 5 days ago (2026-04-10 20:59 UTC)

Technical Summary

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.

Potential Impact

Severity is MEDIUM (CVSS 6.5). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 56/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Before 2 PLUGIN · before-2 Affected: < 2.21.3 Fixed in: 2.21.3
Givewp PLUGIN · givewp Affected: < 2.21.3 Fixed in: 2.21.3
Scroll to top