GivewpWordPress extension
CVE-2023-23672
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 · uneditedMissing Authorization vulnerability in Liquid Web / StellarWP GiveWP.This issue affects GiveWP: 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 confidenceMissing Authorization vulnerability in GiveWP plugin allows unauthenticated or low-privileged users to access donation management functions that should require higher privileges. The specific affected functionality within the plugin is not detailed, but authorization bypasses in WordPress plugins typically involve missing capability checks, nonce verification, or permission checks on admin AJAX endpoints or frontend forms.
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.25.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 versionNavigate to Plugins > Installed Plugins in WordPress admin, find GiveWP, and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/give/includes/plugin.php or the main plugin file.Affected if The displayed version is below 2.25.2 (e.g., 2.25.1, 2.24.x, earlier versions)
-
Confirm plugin is activeCheck the WordPress plugins page to verify GiveWP is currently activated. An inactive plugin does not expose the vulnerability.Affected if GiveWP is installed and activated, and the version check above shows it is below 2.25.2
-
Check for existing donation formsGo to Donations > Forms in the WordPress admin dashboard. Count the number of active donation forms. The vulnerability affects donation management functions, so forms increase the attack surface.Affected if There are active donation forms present while GiveWP is at a vulnerable version
-
Review user role capabilitiesNavigate to Users > Users in WordPress admin. Note any users with roles below Administrator (e.g., Editor, Author, Contributor, Subscriber). The vulnerability allows these lower-privileged users to access higher-privilege donation functions.Affected if Non-administrator user accounts exist while GiveWP is at a vulnerable version
-
Inspect admin AJAX handlersSearch the plugin files in wp-content/plugins/give for AJAX action hooks (add_action with 'wp_ajax_') and check if any donation management actions are missing capability checks (current_user_can). Focus on files in the includes/ directory related to donation processing.Affected if AJAX endpoints handling donation management lack current_user_can() capability checks, confirming the authorization flaw exists in the code
Your environment is affected if GiveWP plugin version is below 2.25.2 and the plugin is active, regardless of whether donation forms or specific user roles are present.
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 · scoped2.25.2
Update GiveWP to the latest version (beyond 2.25.1) which contains the authorization fix. Review user access logs and donation records for any unauthorized modifications during the vulnerable period.
GiveWP 2.25.2
- Backup your WordPress site before making any changes
- Navigate to Plugins > All Plugins in WordPress admin
- Locate GiveWP in the plugin list
- Click 'Update now' if an update is available, or manually upload GiveWP version 2.25.2 or later
- Verify the updated version number reflects 2.25.2 or higher
- Test critical donation workflows to confirm functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Givewp
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23672 — 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-2023-23672 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