CVE-2026-57406
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 · uneditedMissing Authorization vulnerability in Roxnor FundEngine wp-fundraising-donation allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects FundEngine: from n/a through <= 1.7.6.
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 · moderate confidenceMissing authorization vulnerability in the WordPress FundEngine (wp-fundraising-donation) plugin allows attackers to exploit incorrectly configured access control security levels. This likely enables unauthenticated or underprivileged users to access sensitive donation management functions or administrative operations that should require higher privileges.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
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.
-
Confirm FundEngine plugin installationNavigate to WordPress admin dashboard > Plugins and locate 'FundEngine' or 'wp-fundraising-donation' plugin. Note its installed version.Affected if Plugin is installed and running without recent security updates
-
Verify WordPress user role configurationAccess Users > Roles in WordPress admin. Check if any custom roles with elevated FundEngine capabilities were created, or if standard Subscriber/Contributor roles have been granted donation management permissions.Affected if Non-administrator roles have been granted donation management or administrative capabilities beyond their intended scope
-
Inspect plugin capability checksExamine the plugin files (typically in wp-content/plugins/wp-fundraising-donation/) for functions handling donations or admin operations. Look for current_user_can() or capability checks before sensitive operations.Affected if Plugin code lacks proper capability checks on donation handling or admin functions, allowing access without proper authorization
-
Audit donation endpoint accessTest accessing donation management URLs (such as /wp-admin/admin.php?page=... or AJAX endpoints related to donations) using a low-privilege user account or unauthenticated request.Affected if Lower-privileged or unauthenticated users can access donation management functions that should require administrator-level permissions
Environment is affected if the FundEngine plugin is installed and lacks proper capability authorization checks on its donation management or administrative functions.
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 dataImplement proper capability checks and authorization validation on all sensitive functions, particularly those handling donations and admin operations; update to patched version when available.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57406 — 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-57406 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