Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain GiveWP form-editing role
-
DeliveryInject script into donation form template setting
-
ExploitStored payload saved unescaped in HTML attribute
-
ExecutionVictim or admin opens donation form
-
PersistScript executes in browser session
-
ImpactSession hijack or admin-context actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an account already assigned a custom GiveWP role with donation-form-editing capability (PR:H) - this is not available to anonymous visitors or standard subscribers, so the attacker must already be a trusted-but-limited user or have obtained such an account. The payload is stored in one donation form template setting that is output unescaped inside an HTML attribute; execution additionally requires a victim (any site visitor or an administrator) to actually open the affected donation form (UI:R). Limiting factors: the privileged-role prerequisite substantially narrows the attacker population, and the need for a victim to view the specific form gates impact. The flaw affects all GiveWP versions before 4.19.0.1; updating to 4.19.0.1 is the vendor-provided fix. |
| Impact | This is a stored cross-site scripting (CWE-79) flaw in the GiveWP donation plugin, rated CVSS 6.8 (AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H). The signals converge on a moderate, non-urgent priority rather than an emergency. The CVSS vector requires high privileges (PR:H) - specifically a user already granted a custom GiveWP form-editing role - plus victim interaction (UI:R), so it is not a remote-unauthenticated issue. EPSS is low at 0.15% (4th percentile), it is NOT on CISA KEV, and the vuln.today decision label is 'this_month' (not act_now/emergency), all consistent with no observed mass exploitation. A PoC/exploit reference from WPScan exists but is not verified as working exploit code, so public-exploit maturity is unconfirmed. One tension worth noting: the input CVSS assigns C:H/I:H/A:H, which is aggressive for a stored XSS whose real-world impact is typically scoped to the compromised browser session (e.g., hijacking an administrator who opens the form) rather than full confidentiality/integrity/availability loss of the host - treat the 6.8 as a reasonable ceiling and weigh the privilege prerequisite heavily. Net: a real but lower-tier issue, appropriately patched on a routine cycle, not a drop-everything emergency. |
| Exploit ScenarioDerived | An attacker who already holds a custom GiveWP form-editing role (an insider or a lower-trust contributor given form rights) edits a donation form template setting and injects a malicious script into a field that is rendered unescaped inside an HTML attribute. When a site visitor or, more dangerously, a logged-in administrator opens the affected donation form, the script executes in their browser, enabling session/cookie theft or actions in the admin context. A public PoC reference exists but 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
Stored cross-site scripting in GiveWP donation forms before 4.19.0.1 lets a user who already holds a custom GiveWP role with donation-form-editing capability store script in a form template setting, and the script runs in the browser of any visitor or administrator who opens the affected form. The assessed vector is AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N, so the privileged-account prerequisite and the need for victim interaction limit reach; no CISA KEV active exploitation signal is present, and a public PoC reference exists but is not verified as working exploit code.
RemediationAI
Vendor-released patch: GiveWP 4.19.0.1; updating to 4.19.0.1 is the vendor-provided fix for all versions before that release. The supplied sources do not list an alternative workaround, so the primary action is to upgrade; advisory references are https://wpscan.com/vulnerability/59b1b0ff-fbfb-4bb8-883e-94b5f2cee5a4/ and https://nvd.nist.gov/vuln/detail/CVE-2026-111979. Because exploitation requires a custom GiveWP role with donation-form-editing capability and a victim opening the affected form, limiting assignment of such roles to trusted users and reviewing affected donation form template settings reduces exposure while the upgrade is being applied.
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 plugin, and the flaw is CWE-79 (improper neutralization of input during web page generation, cross-site scripting), specifically a stored XSS in one donation form template setting that is output inside an HTML attribute without correct sanitisation or escaping. The supplied CPE cpe:2.3:a:unknown:givewp:*:*:*:*:*:*:*:* and EUVD range 'GiveWP 0 <4.19.0.1' indicate all releases before 4.19.0.1 are affected. The assessed vector AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N matches the stated prerequisites: the attacker needs an authenticated high-privileged role with form-editing rights (PR:H), a victim must open the affected form (UI:R), and the impact is assessed as changed-scope XSS with low confidentiality and integrity impact; the trigger details beyond the unescaped template-setting attribute are not described in the supplied sources.
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:H/UI:R/S:U/C:H/I:H/A:H
Requires a privileged form-editing role (PR:H) and a victim to open the form (UI:R); stored XSS crosses into the victim's browser session (S:C) with limited confidentiality/integrity impact and no availability loss.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The GiveWP WordPress plugin before 4.19.0.1 does not properly sanitise and escape one of its donation form template settings before outputting it inside an HTML attribute, allowing users with a custom form-editing GiveWP WordPress plugin before 4.19.0.1 role to inject arbitrary web scripts that execute in the browser of any visitor or administrator who opens the affected donation form.
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
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
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
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
Path traversal in the GiveWP WordPress plugin before 4.19.0.1 allows an authenticated user holding a high-privilege Give
EUVD-2026-109344
GHSA-xm8r-m35h-qq8p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB