GivewpWordPress extension
CVE-2023-22719
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 Formula Elements in a CSV File vulnerability in 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 · high confidenceGiveWP plugin versions up to 2.25.1 contain a CSV injection vulnerability where malicious formula characters (=, +, -, @, etc.) in donation data are not neutralized before export. When exported CSV files are opened in spreadsheet applications, embedded formulas can execute arbitrary commands on the victim's machine.
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.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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 installed GiveWP versionIn WordPress admin, go to Plugins > Installed Plugins and find GiveWP. The version number is displayed under the plugin name. Alternatively, check the plugin header in wp-content/plugins/give/includes/give.php for 'Version:' value.Affected if The installed version is 2.25.1 or lower.
-
Identify CSV export usageCheck if donation exports are being performed. Look in WordPress admin under Donations > Export, or check server logs for requests to /wp-admin/admin-ajax.php?action=give_export. Review any automated donation reporting scripts that may call GiveWP export functions.Affected if CSV exports of donation data have been generated or are scheduled.
-
Inspect recent CSV exports for formula charactersObtain any recently exported CSV files from GiveWP. Open in a text editor (not Excel) and search for cells beginning with =, +, -, @, tab, or CR characters. These appear at the start of any field value before the first comma.Affected if Any exported CSV contains unescaped formula prefix characters at the start of donation fields.
-
Check custom donation form fieldsReview any custom donation form fields or third-party integrations that feed data into GiveWP. Check if user-submitted values in donor name, email, address, or custom fields could contain formula characters.Affected if Custom fields accept free-form text input that could contain =, +, -, @ characters.
You are affected if GiveWP version is 2.25.1 or lower and CSV exports of donation data have been generated without formula character escaping.
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.
From vendor dataSanitize all user-supplied data in CSV exports by escaping or filtering formula prefix characters (=, +, -, @, tab, CR) to prevent formula injection when files are opened in spreadsheet applications.
Fix this in Givewp
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22719 — 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-22719 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