EUVD-2026-40888
GHSA-mv65-r2jq-jh8q
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain WordPress author credentials
-
DeliveryCraft block_id attribute with XSS payload
-
ExploitInsert givewp_campaign_comments shortcode into post or page
-
InstallPublish or update content
-
C2Victim visits injected page
-
ExecuteStored script executes in victim's browser
-
ImpactSession token or credentials exfiltrated
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 authenticated WordPress session with author-level access or higher (PR:L in CVSS terms). The GiveWP plugin must be installed, active, and at version 4.16.0 or earlier. The Campaigns feature within GiveWP must be in use, as the vulnerability resides specifically in the givewp_campaign_comments shortcode and its block rendering pipeline. The attacker must have permission to create or edit posts/pages that include shortcodes. Exploitation is limited by the author-level authentication barrier - anonymous or subscriber-level users cannot trigger this path. Standard WordPress installs where only trusted administrators hold author roles are not practically at risk, but sites granting author access to volunteers, fundraising coordinators, or external contributors face real exposure. |
| Impact | The CVSS 3.1 base score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects a medium-severity stored XSS with changed scope, consistent with persistent cross-user impact. The PR:L metric accurately captures the author-level authentication barrier, which meaningfully limits the exposed attack surface compared to unauthenticated XSS. The S:C (Scope Changed) metric is appropriate because the vulnerability's impact extends from the web application to the browsers of site visitors. The UI:N designation - non-standard for XSS in some scoring traditions - is defensible here because once the payload is stored, no further attacker interaction is required; victim browsing is incidental rather than socially engineered. EPSS data was not provided, so exploitation probability cannot be quantified. No KEV listing and no confirmed POC reduce urgency. Real-world risk is moderate: it is constrained by the author-level prerequisite, but any organization running GiveWP with author-or-above roles assigned to untrusted users (e.g., guest bloggers, volunteer fundraising staff) faces meaningful risk of privilege escalation or session hijacking. |
| Exploit ScenarioDerived | An attacker with a WordPress author account on a GiveWP-powered site creates or edits a post or page containing the givewp_campaign_comments shortcode and sets the block_id attribute to a value that breaks out of the single-quoted HTML attribute context, embedding a script tag. The payload is stored server-side and executes in the browser of every visitor who loads that page, enabling session cookie theft, credential harvesting overlays, or unauthorized actions on behalf of the victim. No public exploit code has been identified, but the vulnerability is straightforward to exploit given the clear source code references published in the CVE. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Stored Cross-Site Scripting in GiveWP versions up to and including 4.16.0 allows authenticated attackers with author-level WordPress access to inject persistent JavaScript payloads via the 'block_id' attribute of the 'givewp_campaign_comments' shortcode. The flaw originates in two code paths - CampaignCommentsShortcode::parseAttributes() and BlockRenderController::render() - where the blockId value is interpolated directly into a single-quoted HTML attribute without WordPress's esc_attr() sanitization function. Any visitor loading an injected page will have the malicious script execute in their browser context. No active exploitation is confirmed (not in CISA KEV) and no public exploit code has been identified at time of analysis.
RemediationAI
A fix is available via WordPress plugin Trac changeset 3590193 (https://plugins.trac.wordpress.org/changeset?old=3590193%40give&new=3590193%40give), which represents an upstream code correction. The exact released version number containing this fix is not confirmed in the available reference data; administrators should update GiveWP to the latest version available in the WordPress Plugin Directory and verify the installed version exceeds 4.16.0. As a compensating control while patching, restrict WordPress author-level and above roles to fully trusted users only, since the vulnerability requires an authenticated session at that privilege level. Additionally, a Web Application Firewall rule blocking attribute-breaking characters (single quotes, angle brackets) in shortcode parameters can reduce exploitation risk but may interfere with legitimate shortcode use. Disabling the Campaigns feature entirely, if not operationally required, eliminates the vulnerable code path with no impact to core donation functionality.
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 and fundraising plugin developed by StellarWP (CPE: cpe:2.3:a:stellarwp:givewp_-_donation_plugin_and_fundraising_platform:*:*:*:*:*:*:*:*). The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation - Stored XSS). The vulnerability exists in the Campaigns feature, specifically in two classes: CampaignCommentsShortcode (plugins.trac.wordpress.org/browser/give/tags/4.16.0/src/Campaigns/Shortcodes/CampaignCommentsShortcode.php#L17 and #L78) and BlockRenderController (plugins.trac.wordpress.org/browser/give/tags/4.16.0/src/Campaigns/Blocks/CampaignComments/Controller/BlockRenderController.php#L23). The shortcode is registered via RegisterCampaignShortcodes and rendered through render.php. WordPress provides the esc_attr() function precisely to neutralize attribute-context injection, but the blockId value bypasses this filter entirely, making the single-quoted HTML attribute boundary breakable with a crafted attribute payload.
Know when Wordpress Plugin 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:L/UI:N/S:C/C:L/I:L/A:N
Author-level authentication (PR:L) is required; stored payload executes on any visitor without further attacker action (UI:N); scope change (S:C) reflects cross-user browser impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'block_id' (and other) shortcode attributes of the 'givewp_campaign_comments' shortcode in versions up to, and including, 4.16.0. This is due to insufficient input sanitization and output escaping on user supplied attributes in CampaignCommentsShortcode::parseAttributes() and BlockRenderController::render(), where the blockId value is interpolated directly into a single-quoted HTML attribute without esc_attr(). This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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.
Related Vulnerabilities in GiveWP Plugin CSRF and Stored XSS Vulnerabilities
View all 2More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Exploit-DB