Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLoad public shortcode page
-
DeliveryHarvest exposed nonce from wallets_data
-
ExploitSend crafted cdbbc_payment_verify AJAX request
-
ExecutionStore malicious data_object payload
-
PersistAdmin views donation list table
-
ImpactScript executes in admin browser
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 that a public-facing page renders the [crypto-donation-box] shortcode, which both exposes the cdbbc_donation_box nonce in the wallets_data JavaScript object and makes the wp_ajax_nopriv_cdbbc_payment_verify action reachable by anonymous users - these are default behaviors wherever the donation box is published, so no non-default configuration is needed. No authentication is required (PR:N confirmed) and no victim interaction is needed to inject the payload. The practical limiting factor is the second-order nature of stored XSS: the injected script only fires when a logged-in user - typically an administrator - opens the plugin's donation list table in wp-admin, so impact is gated on that admin view occurring rather than on any attacker-controlled step. |
| Impact | This is a genuine, defensible priority within its (niche) deployment base, though not a mass-exploitation emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2 HIGH) is internally consistent with the description: the flaw is reachable over the network with low complexity and no privileges because the cdbbc_payment_verify handler is registered under wp_ajax_nopriv_ and its sole nonce gate is bypassable (the cdbbc_donation_box nonce is leaked to anonymous visitors in the wallets_data JS object from the [crypto-donation-box] shortcode). The scope-change (S:C) and C:L/I:L/A:N impacts correctly model stored XSS executing in other users' browser context rather than compromising the server directly. Exploitation status: no public exploit identified at time of analysis - there is no KEV listing and no POC flag in the input, so there is no evidence of active exploitation or weaponization. EPSS was not provided, so exploitation probability cannot be quantified. The authentication assessment is firmly grounded: PR:N confirms unauthenticated reachability, reinforced by the description's explicit nopriv/nonce-bypass mechanism. Net: a real, confirmable unauthenticated stored-XSS requiring remediation on affected sites, but its real-world blast radius is bounded by the plugin's limited footprint rather than by any technical difficulty of exploitation. |
| Exploit ScenarioDerived | An unauthenticated attacker visits a public page containing the [crypto-donation-box] shortcode, scrapes the exposed cdbbc_donation_box nonce from the wallets_data JavaScript object, and sends a crafted cdbbc_payment_verify AJAX request with a malicious data_object value. The unsanitized payload is stored and later rendered in the plugin's admin donation list table (cdbbc-list-table.php), so the injected script executes in the browser of an administrator who views the donations page. No public exploit code is identified at time of analysis, but the attack path is fully described in the Wordfence advisory. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Stored cross-site scripting in the Cryptocurrency Donation Box plugin for WordPress (all versions up to and including 2.2.13) allows unauthenticated attackers to persist arbitrary JavaScript via the data_object parameter of the cdbbc_payment_verify AJAX action, which executes whenever a user opens an injected page. The plugin registers that AJAX action under wp_ajax_nopriv_ and its only gate is a nonce that is publicly exposed to anonymous visitors inside the wallets_data JavaScript object emitted by the [crypto-donation-box] shortcode, so exploitation needs no credentials (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C, score 7.2) and no non-default configuration - any site publishing the shortcode is exposed. Impact is gated on the second-order step: the injected script fires when a logged-in user, typically an administrator, views the plugin's donation list table in wp-admin. No public exploit code or confirmed active exploitation is identified at time of analysis, and the practical exposure is limited to sites running this niche plugin.
RemediationAI
No vendor-released patch was identified in the provided data; the only code references are the plugin's Trac browser views of its trunk sources rather than a tagged fixed release, so patch status should be confirmed directly against the plugin's WordPress.org page and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/9c3724f3-ebd9-4804-88e0-804fd423af3a?source=cve before assuming a fix exists. If no fixed version is available, the most effective action is to deactivate and remove the plugin entirely - the trade-off is loss of crypto donation functionality on the site. A less drastic but still effective mitigation is to remove the [crypto-donation-box] shortcode from all public-facing pages, which denies anonymous visitors the cdbbc_donation_box nonce and makes the wp_ajax_nopriv_cdbbc_payment_verify route unreachable from outside; the side effect is that the donation box stops rendering anywhere it is needed. Because the injected payload only fires when a logged-in user opens the plugin's donation list table in wp-admin, restricting access to wp-admin (IP allow-listing, HTTP auth in front of /wp-admin) limits the trigger opportunity but does not remove the stored payload and adds operational friction for administrators. A WAF or request-filtering rule that rejects POST bodies to admin-ajax.php containing script markup in the data_object parameter provides interim protection for hosts that cannot immediately change plugin configuration, though such rules are signature-based and can be bypassed by encoding tricks. Once a fixed release is published, upgrade immediately and then review wp-admin donation records for previously injected script content, since stored payloads persist in the database and survive a code-level fix.
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
The flaw is a CWE-79 stored (second-order) cross-site scripting issue in the WordPress plugin 'Cryptocurrency Donation Box - Bitcoin & Crypto Donations' (CPE cpe:2.3:a:blackworks1:cryptocurrency_donation_box_-_bitcoin_&_crypto_donations), caused by insufficient input sanitization of the data_object request parameter combined with missing output escaping when that value is rendered. The attack surface is a WordPress AJAX endpoint: the plugin registers wp_ajax_nopriv_cdbbc_payment_verify, meaning anonymous requests are routed to the handler without any WordPress capability check. The handler's only authentication gate is a nonce verification against cdbbc_donation_box; however, the plugin emits that same nonce to unauthenticated visitors within the wallets_data JavaScript object generated by the [crypto-donation-box] shortcode, so the nonce provides no protection and is trivially harvested from any public page that renders the shortcode. The unescaped value is later stored and output in the plugin's admin list table (referenced source: admin/table/cdbbc-list-table.php, near line 109), which is why the payload executes in an administrative browsing context - the classic privileged-context stored XSS pattern. The CVSS scope change (S:C) reflects that script executing in the wp-admin origin can reach beyond the vulnerable plugin component, for example via the authenticated admin session. Relevant source references cited by the reporter include includes/cdbbc-payment-verify.php (lines 57 and 98), cryptocurrency-donation-box.php (line 83) and includes/cdbbc-shortcode.php (line 75), which correspond to the AJAX registration, the nonce handling, and the shortcode that leaks the nonce.
Know when Cryptocurrency Donation Box Bitcoin Crypto Donations 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:C/C:L/I:L/A:N
Unauthenticated network injection via bypassable nopriv AJAX nonce (PR:N/AC:L/UI:N); stored XSS executes in a separate security scope (S:C) with limited C/I impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Cryptocurrency Donation Box - Bitcoin & Crypto Donations plugin for WordPress is vulnerable to Stored Cross-Site Scripting via data_object Parameter in all versions up to, and including, 2.2.13 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by unauthenticated attackers because the cdbbc_payment_verify AJAX action is registered under wp_ajax_nopriv_ and its only authentication gate - a nonce check - is bypassable, as the cdbbc_donation_box nonce is publicly exposed to anonymous visitors via the wallets_data JavaScript object emitted by the [crypto-donation-box] shortcode.
Executive ViewAI
The Cryptocurrency Donation Box plugin for WordPress - present on any site that publishes its donation shortcode - contains a stored cross-site scripting flaw affecting all versions up to and including 2.2.13, allowing unauthenticated visitors to plant persistent malicious scripts in the site's database. Those scripts execute in the browser of a logged-in administrator reviewing the plugin's donation records, which could hand an attacker control of an authenticated admin session and, by extension, the entire website. With no vendor patch available and no non-default configuration required, every organization running this plugin should assume its public-facing WordPress presence is exposed until the plugin is removed or mitigated.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or uninstall the Cryptocurrency Donation Box plugin entirely, or remove the [crypto-donation-box] shortcode so the exposed nonce and AJAX action are no longer emitted; block or filter requests to admin-ajax.php with the cdbbc_payment_verify action or script content in the data_object parameter at the WAF/reverse proxy; restrict wp-admin access by IP allowlisting or additional authentication so injected scripts are less likely to reach an administrator session; monitor and sanitize the plugin's donation database tables for stored script payloads; and rotate administrator credentials and sessions until the plugin is removed or patched.
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.
EUVD-2026-100790
GHSA-848q-gjxc-xwwm
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB