CVE-2026-4650
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FundPress WordPress donation plugin up to v2.0.8 has an authorization bypass in its donate_action_status() AJAX handler. This endpoint is exposed to unauthenticated users (wp_ajax_nopriv) and only validates that a schema parameter equals 'donate-ajax' and POST parameters are present, but fails to verify user capabilities, nonce tokens, or ownership. Attackers can enumerate sequential donation IDs to modify any donation's status (completed, pending, cancelled), potentially triggering unwanted email notifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify FundPress plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and check if FundPress is listed. Note the installed version number. Compare to the affected range: versions up to and including v2.0.8 are vulnerable.Affected if FundPress is installed with version 2.0.8 or lower
-
Check for exposed AJAX endpoint registrationSearch the plugin files (typically in wp-content/plugins/fundpress-donation) for 'donate_action_status' and 'wp_ajax_nopriv' to see if the vulnerable AJAX handler is registered for unauthenticated access. Look in the main plugin PHP file or initialization code.Affected if The code registers donate_action_status with wp_ajax_nopriv, exposing it to unauthenticated users
-
Inspect the donate_action_status handler for authorization gapsLocate the donate_action_status() function in the plugin code. Examine whether it contains capability checks (like current_user_can), nonce verification (like wp_verify_nonce), or donation ownership validation before allowing status modifications.Affected if The handler function lacks capability checks, nonce validation, and ownership verification for the donation ID being modified
-
Test AJAX endpoint accessibilitySend a crafted POST request to /wp-admin/admin-ajax.php with action=donate_action_status and a schema parameter set to 'donate-ajax', along with any required POST parameters. Observe if the server processes the request without requiring authentication.Affected if The endpoint accepts and processes requests without requiring authentication or valid session cookies
A user is affected if FundPress plugin version 2.0.8 or lower is installed and the donate_action_status AJAX endpoint is exposed to unauthenticated users without proper authorization, capability checks, or ownership validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAdd proper authorization checks, nonce verification, and donation ownership validation to the donate_action_status() AJAX handler. Only permit users with appropriate capabilities to modify donation statuses, and verify the requesting user owns or has rights to the specific donation ID being modified.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data