Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAccess public GiveWP donation form
-
ExploitSubmit donation with mismatched currency
-
ExecutionBypass bare-number amount comparison
-
ImpactRecord donation below configured minimum/fixed amount
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Requires a GiveWP donation form (before 4.19.0.1) that has a configured minimum or fixed donation amount - that configured floor is the exact feature being bypassed. Exploitation works against default behavior with no authentication (PR:N), no user interaction, and no special attacker privileges: the attacker submits a donation specifying a currency other than the one the site/form accepts, so the amount is compared as a bare number and clears the limit. The principal limiting factor is impact scope: the outcome is only that a donation can be made below the intended minimum/fixed value (integrity of donation records/accounting); there is no data disclosure or availability impact, and forms without a configured minimum or fixed amount have nothing to bypass. |
| Impact | This is a moderate, low-urgency business-logic flaw rather than a top-priority emergency. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N = 5.3 Medium) is internally consistent with the description: remote, unauthenticated, low-complexity, no user interaction, and only a low integrity impact (C:N, A:N). It is NOT in CISA KEV and no EPSS score was supplied, so widespread or automated exploitation is not evidenced. The only exploitation signal is a single WPScan reference labeled as an exploit, but the input marks it as reference-only, not verified working exploit code - so a public PoC reference exists; it is not verified as working exploit code. The vuln.today decision label is 'this_month', consistent with medium severity and no confirmed active exploitation. The practical impact is financial/accounting integrity (donations accepted below a form's configured minimum or fixed amount) rather than data theft or code execution; the 'Information Disclosure' tag conflicts with the C:N vector and appears mislabeled. Net: a real but low-impact issue worth patching on a normal monthly cycle, not an incident-response-grade priority. |
| Exploit ScenarioDerived | An unauthenticated visitor submits a donation to a GiveWP form whose currency differs from the amount the form validates, so that the raw numeric amount falls below the form's configured minimum or fixed donation value. Because GiveWP compares the amount as a bare number without normalizing for currency, the under-minimum donation is accepted. A public PoC reference exists (WPScan); it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
An unauthenticated visitor to a WordPress site running the GiveWP donation plugin before 4.19.0.1 can push a donation through below the amount floor the form is configured to enforce, by specifying a currency that the site or form does not actually accept. The plugin compares the donation amount to its minimum or fixed value as a bare number, so the mismatched currency slips past the check and the donation is recorded at a value the site owner intended to reject, affecting the integrity of donation records and accounting rather than exposing data or disrupting availability. A public PoC reference exists; it is not verified as working exploit code, and no confirmed active exploitation has been reported; the assessed CVSS is 5.3 with PR:N (unauthenticated) and no user interaction, and exploitation only matters on forms that actually configure a minimum or fixed donation amount.
RemediationAI
Upgrade the GiveWP WordPress plugin to 4.19.0.1 or later, which is the version boundary at which the currency/amount validation issue is addressed; confirm the installed version in the WordPress plugins screen or via WP-CLI and verify the update actually applied on any site using donation forms with minimum or fixed amounts. The WPScan advisory at https://wpscan.com/vulnerability/2d7c0c89-7f0e-4f2b-908f-7d96e1d8a228/ is the reference for affected versions and the fix. Because exploitation requires only a publicly reachable donation form and no credentials, sites that cannot update immediately should review donation form configurations and scrutinize or reconcile recorded donations whose amounts fall below the configured minimum or whose currency does not match the form's accepted currency; forms that do not set a minimum or fixed donation amount have nothing for this flaw to bypass and therefore carry no meaningful exposure. Given the assessed integrity-only impact and this-month priority, treat any below-minimum or mismatched-currency donations already in the records as an accounting reconciliation task rather than a host-compromise incident.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
GiveWP is a WordPress donation/e-commerce plugin whose forms can enforce a minimum donation or a fixed donation amount, with the amount denominated in the currency the site or form accepts. The weakness is a business-logic validation flaw: the currency of an incoming donation is not constrained to the site's or form's accepted currency, yet the amount is still compared against the configured minimum or fixed value as a bare number, so a submission in a different currency clears the limit while the underlying amount check is meaningless. With a CVSS:3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, the flaw is remotely reachable over the network, requires no authentication and no user interaction, and stays within the vulnerable component, with impact limited to integrity; there is no confidentiality or availability effect. The supplied data provides no CWE mapping, and the trigger is limited to forms that have a configured minimum or fixed donation amount - a form without such a floor has nothing to bypass. The CPE string cpe:2.3:a:unknown:givewp:*:*:*:*:*:*:*:* is a wildcard, so the exact version inventory should be confirmed against the installed plugin version and the WPScan advisory.
Know when Givewp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Remote, unauthenticated, low-complexity submission with no user interaction (AV:N/AC:L/PR:N/UI:N); only donation-amount integrity is affected (I:L), with no confidentiality or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The GiveWP WordPress plugin before 4.19.0.1 does not restrict the currency of a donation to the one the site or form accepts, while comparing its amount limits as bare numbers, allowing unauthenticated users to make donations below a form's configured minimum or fixed amount.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
Unauthenticated PHP object injection in the GiveWP WordPress donation plugin (all versions through 4.16.7.1) lets remote
Improper privilege management in the GiveWP WordPress donation plugin (affected ranging from 4.16.6 up to but not includ
GiveWP WordPress plugin before 4.16.3 exposes sensitive donor privacy data through an unauthenticated REST API endpoint
Stored cross-site scripting in the GiveWP WordPress plugin before version 4.16.3 allows authenticated users holding the
Stored cross-site scripting in GiveWP donation forms before 4.19.0.1 lets a user who already holds a custom GiveWP role
The Donations Widget plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.
The GiveWP WordPress plugin before 2.21.3 does not have CSRF in place when exporting data, and does not validate the exp
The GiveWP WordPress plugin before 2.17.3 does not escape the json parameter before outputting it back in an attribute i
The GiveWP - Donation Plugin and Fundraising Platform WordPress plugin before 2.10.0 was affected by a reflected Cross-S
The "Donation Plugin and Fundraising Platform" plugin before 2.3.1 for WordPress has wp-admin/edit.php csv XSS. Rated me
EUVD-2026-109634
GHSA-2rxp-vx6w-qq2v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB