dbcve.org
GivewpWordPress extension

CVE-2022-40312

MEDIUM · 6.5 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 2.25.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A Server-Side Request Forgery (SSRF) vulnerability exists in the GiveWP WordPress donation plugin versions up to 2.25.1. The vulnerability allows an attacker to make the server perform unintended requests to internal or external resources due to insufficient validation of user-supplied URLs in donation-related functionality.

MitigationUpdate GiveWP to the latest patched version (2.25.2 or later). If immediate update is not possible, restrict outbound network access from the web server and implement URL allowlisting for any donation webhook or callback features.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GivewpWordPress extension
Affected:<= 2.25.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify GiveWP plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'GiveWP - Donation Plugin' or check the plugins directory for the GiveWP files
    Affected if GiveWP plugin is present on the WordPress site
  2. Check installed GiveWP version
    In WordPress admin, go to Plugins > Installed Plugins, find GiveWP, and note the version number displayed. Alternatively, check the main plugin file header in wp-content/plugins/give/src/Plugin.php for the 'Version' constant
    Affected if Version is 2.25.1 or lower
  3. Identify donation forms with webhook or callback URLs
    Go to Donations > All Forms, review each donation form settings, and check for any fields accepting URLs such as webhook URLs, callback endpoints, or custom redirect URLs under form settings or payment gateway configuration
    Affected if Donation forms exist with webhook/callback URL fields configured and accessible to users
  4. Check for recent suspicious outbound requests
    Review web server access logs and application logs for unusual outbound requests originating from the WordPress server, particularly look for requests to internal IP ranges (10.x.x.x, 192.168.x.x, 127.x.x.x) or cloud metadata endpoints that occurred after donation form submissions
    Affected if Outbound requests to internal resources or unexpected destinations are found in logs following donation activity

A site is affected if it runs GiveWP version 2.25.1 or lower and has donation forms that accept user-supplied URLs for webhooks, callbacks, or similar features.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2.25.1
Interim mitigation

Update GiveWP to the latest patched version (2.25.2 or later). If immediate update is not possible, restrict outbound network access from the web server and implement URL allowlisting for any donation webhook or callback features.

Recommended fix Moderate confidence

GiveWP 2.25.2 or later (latest stable version)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Locate GiveWP (GiveWP – Donation Plugin and Fundraising Platform)
  4. 4. If an update is available, click 'Update Now' to update to the latest version (2.25.2 or newer)
  5. 5. Alternatively, download the latest GiveWP version from the official WordPress repository or the vendor's website
  6. 6. After updating, verify the plugin version in the plugins list to confirm the update succeeded
  7. 7. Test donation functionality to ensure the plugin continues to work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Givewp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40312 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data