GivewpWordPress extension
CVE-2024-27987
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.3.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 confidenceCross-site scripting (XSS) vulnerability in GiveWP donation plugin allows injection of malicious scripts via unsanitized user input that gets rendered in web pages without proper output encoding.
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.4.0CVSS 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.
-
Confirm GiveWP plugin is installedCheck your WordPress site's plugins directory or admin panel for the GiveWP donation pluginAffected if GiveWP plugin is present on the WordPress site
-
Identify the installed GiveWP versionAccess the WordPress admin panel under Plugins > Installed Plugins and locate GiveWP, then note the displayed version number. Alternatively, check the version in the plugin's main PHP file header or composer.json if accessible via file systemAffected if The version number is lower than 3.4.0 (e.g., 3.3.x, 3.2.x, etc.)
-
Verify donation forms are activeCheck if any donation forms are published and accessible on the site. Visit the public-facing donation pages to confirm they load and accept user inputAffected if Donation forms are published and accessible to users (this is the default state)
-
Inspect form input fields for output encodingSubmit a test donation with a harmless test string containing special characters (e.g., <script>test</script>) in common fields like name, email, or donation amount notes, then view the page source or inspect the rendered output to see if the characters are encoded or executedAffected if The special characters render as plain text (unencoded) or the script executes in the browser output
You are affected if GiveWP version is below 3.4.0 and donation forms are active and rendering user-submitted data without encoding.
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.4.0
Update GiveWP to the patched version. Until then, disable or restrict donation form submissions from untrusted sources and implement additional input sanitization on the web server level.
3.4.0
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find GiveWP in the plugin list
- Click 'Update now' if an update is available, or manually upload version 3.4.0
- Verify the update completed successfully
- Test critical donation workflows to ensure functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Givewp
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-27987 — 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-27987 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