CVE-2026-4650 json
FundPress <= 2.0.8 - Missing Authorization to Unauthenticated Arbitrary Donation Status Modification via donate_action_status AJAX Handler
published 6mo ago modified 4mo ago also EUVD-2026-26755
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
The FundPress – WordPress Donation Plugin for WordPress is vulnerable to authorization bypass in versions up to and including 2.0.8. This is due to missing authorization and nonce verification in the donate_action_status() AJAX handler, which is registered to be accessible to unauthenticated users via wp_ajax_nopriv. The function only validates that the schema parameter equals 'donate-ajax' and that the required POST parameters are present, but fails to verify user capabilities, nonce tokens, or donation ownership. This makes it possible for unauthenticated attackers to modify the status of any donation by providing its ID (which are sequential integers and easily enumerable), allowing them to mark donations as completed, pending, cancelled, or any arbitrary status, potentially triggering email notifications and related side effects.
Is CVE-2026-4650 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- thimpress FundPress – WordPress Donation Plugin
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/5db3c66f-0a9c-4233-923c-0965dec68c60?source=cve
- plugins.trac.wordpress.org /browser/fundpress/trunk/inc/class-dn-ajax.php#L179
- plugins.trac.wordpress.org /browser/fundpress/tags/2.0.8/inc/class-dn-ajax.php#L179
- plugins.trac.wordpress.org /browser/fundpress/trunk/inc/class-dn-ajax.php#L173
- plugins.trac.wordpress.org /browser/fundpress/tags/2.0.8/inc/class-dn-ajax.php#L173
- plugins.trac.wordpress.org /browser/fundpress/trunk/inc/class-dn-donate.php#L189
- plugins.trac.wordpress.org /browser/fundpress/tags/2.0.8/inc/class-dn-donate.php#L189
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3502937%40fundpress&new=3502937%40fundpress&sfp_email=&sfph_mai
- plugins.trac.wordpress.org /browser/fundpress/tags/2.0.9/inc/class-dn-ajax.php#L179
Sources
- CVE List CVE-2026-4650
- NVD CVE-2026-4650
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.