LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40312: WordPress GiveWP Plugin <= 2.25.1 is vulnerable to Server Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) vulnerability in GiveWP GiveWP – Donation Plugin and Fundraising Platform.This issue affects GiveWP – Donation Plugin and Fundraising Platform: from n/a through 2.25.1.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-40312 is an SSRF issue in the WordPress GiveWP donation plugin through version 2.25.1. A successful attack could make the website server send unintended requests, with limited confidentiality, integrity, and availability impact. The CVSS data indicates exploitation needs high privileges and high complexity.

Executive priority

Treat this as a moderate-priority WordPress plugin issue. It is not cited as actively exploited, but donation sites can be business-critical and public-facing, so affected installations should be identified and moved out of the vulnerable range promptly.

Technical view

The issue is categorized as CWE-918 server-side request forgery in GiveWP. The CVSS 3.1 vector is AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L, scoring 5.5. Sources identify affected versions through 2.25.1 but do not provide exploit details or a specific fixed release in the supplied bundle.

Likely exposure

Exposure is limited to WordPress sites running GiveWP Donation Plugin and Fundraising Platform version 2.25.1 or earlier. Risk is higher where many users have high-privilege WordPress access.

Exploitation context

The supplied sources do not show CISA KEV listing or active exploitation. The CVSS vector suggests an attacker needs high privileges, no user interaction, and must overcome high attack complexity.

Researcher notes

Evidence is limited to the CVE record and PatchStack reference. The bundle does not include endpoint details, proof-of-concept material, exploit telemetry, or a named fixed version. Avoid assuming broader product impact beyond GiveWP through 2.25.1.

Mitigation direction

  • Inventory WordPress sites using the GiveWP plugin.
  • Move installations off GiveWP 2.25.1 or earlier following vendor guidance.
  • Check PatchStack and vendor advisories for the confirmed fixed version.
  • Limit high-privilege WordPress accounts to trusted administrators.
  • Review server outbound request monitoring for unusual plugin-originated traffic.

Validation and detection

  • Confirm installed GiveWP versions across production and staging WordPress sites.
  • Verify no site remains on GiveWP 2.25.1 or earlier.
  • Review administrator account assignments and recent privileged access changes.
  • Check web server egress logs for unexpected internal or external requests.
  • Document remediation status and any accepted residual risk.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-40312 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L1.33.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-40312Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GiveWPGiveWP – Donation Plugin and Fundraising Platformgive, n/aunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.