CVE-2026-39691
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 AdAstraCrypto Cryptocurrency Donation Box – Bitcoin & Crypto Donations cryptocurrency-donation-box allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Cryptocurrency Donation Box – Bitcoin & Crypto Donations: from n/a through <= 2.2.13.
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 confidenceA missing authorization vulnerability in the Cryptocurrency Donation Box WordPress plugin (versions up to 2.2.13) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to donation management functions or sensitive operations due to missing permission checks on certain endpoints or actions.
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.
-
Identify plugin installation and versionNavigate to WordPress admin dashboard > Plugins > Installed Plugins and locate 'Cryptocurrency Donation Box - Bitcoin & Crypto Donations' by AdAstraCrypto. Note the installed version number displayed.Affected if The plugin is installed and the version is 2.2.13 or lower.
-
Verify WordPress user role for sensitive actionsAs a low-privilege user (e.g., Subscriber or Contributor), attempt to access donation management features or admin-specific URLs within the plugin (e.g., /wp-admin/admin.php?page=adastra_crypto_donations or similar plugin admin endpoints).Affected if A non-administrator user can access administrative or donation management functions without being prompted for authorization.
-
Test direct object reference vulnerabilityUse a web proxy or browser to directly request plugin AJAX endpoints or form actions related to donations (such as those handling fund transfers, withdrawal requests, or user data modification) while authenticated as an unprivileged user.Affected if The endpoint returns successful responses or performs actions without verifying the user has administrative privileges.
-
Inspect plugin capabilities configurationCheck the plugin's source code files (if accessible via FTP or file manager) in /wp-content/plugins/ for any capability checks before sensitive operations. Look for 'current_user_can' or 'capability' definitions in the main plugin PHP file.Affected if The plugin code lacks capability checks before executing donation management, fund transfers, or administrative actions.
The environment is affected if the Cryptocurrency Donation Box plugin version is 2.2.13 or lower and sensitive functionality is accessible without proper WordPress role verification.
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 role-based access control (RBAC) and authorization checks on all sensitive functions, verifying user permissions before allowing access to donation creation, modification, or management features.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39691 — 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-39691 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