CVE-2025-49899
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 jjlemstra Whydonate wp-whydonate allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Whydonate: from n/a through <= 4.0.15.
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 Whydonate WordPress plugin (wp-whydonate). The plugin fails to properly enforce Access Control Lists (ACLs) on certain functionality, allowing unauthenticated or unauthorized users to access features that should be restricted to privileged users. This is a Broken Access Control (BAC) issue classified under CWE-862.
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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Verify Whydonate plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Whydonate' or 'wp-whydonate' in the list of active pluginsAffected if The Whydonate plugin appears in the installed plugins list
-
Determine installed plugin versionClick 'View details' on the Whydonate plugin in the WordPress plugins page, or check the plugin's main PHP file (typically wp-content/plugins/wp-whydonate/plugin-name.php) for the 'Version' header in the plugin comment blockAffected if The installed version is 4.0.15 or lower
-
Compare version against affected rangeCompare your installed version number to the affected range: any version from the plugin's initial release through version 4.0.15 (inclusive) is considered vulnerableAffected if Your version is 4.0.15 or any earlier version
-
Identify exposed sensitive endpointsReview WordPress access logs or use a security scanner to test common admin-action endpoints (such as those handling donation processing, user management, or fund distribution) without providing authentication credentialsAffected if Sensitive functionality returns successful responses without requiring login or admin privileges
You are affected if the Whydonate plugin is installed and your installed version is 4.0.15 or lower, as this version range lacks proper authorization checks on sensitive 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 authorization checks (capability verification, nonce validation, role-based access control) on all sensitive functions and admin pages. Upgrade to a patched version of the plugin beyond 4.0.15 once available.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49899 — 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-2025-49899 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