GivewpWordPress extension
CVE-2024-35679
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in StellarWP GiveWP give.This issue affects GiveWP: from n/a through <= 3.12.0.
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 confidenceCross-site scripting (XSS) vulnerability in GiveWP plugin allows injection of malicious scripts through improper neutralization of user input during web page generation. The vulnerability affects versions through 3.12.0.
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
< 3.12.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Check GiveWP plugin versionLog in to WordPress admin dashboard, navigate to Plugins > Installed Plugins, find GiveWP in the list and check the version number displayed below the plugin name. Alternatively, check the main plugin file (givewp.php) in wp-content/plugins/give/ for the 'Version' header in the file comments.Affected if The installed version is less than 3.12.1 (for example, 3.12.0, 3.11.x, or earlier)
-
Verify GiveWP is activeIn WordPress admin under Plugins > Installed Plugins, confirm that GiveWP shows as 'Active' rather than 'Inactive'.Affected if GiveWP plugin is active and version is below 3.12.1
-
Identify active donation formsIn WordPress admin, go to Donations > All Forms and review the list of published donation forms. Note which forms accept user-supplied input in custom fields, donor comments, or custom amount fields.Affected if Any donation form is published and accepting user input, and the GiveWP version is vulnerable
Your environment is affected if GiveWP plugin version is below 3.12.1 and the plugin is active with published donation forms that accept user input.
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 · scoped3.12.1
Update GiveWP to the latest version beyond 3.12.0 which should contain the security patch, or implement proper input sanitization and output encoding for all user-supplied data before rendering in the browser.
GiveWP 3.12.1
- Create a full backup of your WordPress site and database before making any changes
- Log into your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the GiveWP plugin in the list
- If an update is available, click 'Update Now' to update to version 3.12.1
- Alternatively, go to Dashboard > Updates and select GiveWP to update
- After updating, verify the plugin version shows 3.12.1 under the plugin name
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Givewp
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35679 — 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-2024-35679 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