GivewpWordPress extension
CVE-2022-2117
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 · uneditedThe GiveWP plugin for WordPress is vulnerable to Sensitive Information Disclosure in versions up to, and including, 2.20.2 via the /donor-wall REST-API endpoint which provides unauthenticated users with donor information even when the donor wall is not enabled. This functionality has been completely removed in version 2.20.2.
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 · high confidenceThe GiveWP WordPress plugin versions up to 2.20.2 contain a sensitive information disclosure vulnerability in the /donor-wall REST-API endpoint. This endpoint allows unauthenticated users to query and receive donor information (names, emails, donation amounts) even when the donor wall feature is disabled, exposing personal data without authentication.
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
<= 2.20.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GiveWP plugin versionLog into WordPress admin, go to Plugins > Installed Plugins > Find GiveWP and note the version number. Alternatively, use WP-CLI: wp plugin list --name=givewpAffected if Version is 2.20.2 or lower
-
Test /donor-wall REST-API endpoint accessibilitySend a GET request to your site's /wp-json/givewp/v1/donor-wall endpoint (example: curl -s https://yourdomain.com/wp-json/givewp/v1/donor-wall)Affected if The endpoint returns a 200 OK response with any JSON data, regardless of whether the Donor Wall feature is enabled in GiveWP settings
-
Verify sensitive donor data exposureExamine the JSON response from the previous step. Look for fields containing donor names, email addresses, donation amounts, or other personally identifiable informationAffected if The response contains any donor names, email addresses, or donation amounts without requiring authentication
You are affected if GiveWP version is 2.20.2 or lower AND the /donor-wall REST-API endpoint is accessible and returns donor information without authentication.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate GiveWP to version 2.20.2 or later where the vulnerable REST-API endpoint has been completely removed. If immediate updating is not possible, consider blocking the /donor-wall REST-API route at the web server level.
GiveWP version 2.20.2 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the GiveWP plugin in the list
- Check if the current version is 2.20.2 or below
- If vulnerable, click 'Update Now' to upgrade to version 2.20.2 or later
- Alternatively, download the latest version from wordpress.org/plugins/give and upload via Plugins > Add New > Upload Plugin
- After update, verify the version number reflects 2.20.2 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Givewp
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2117 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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