CVE-2025-10186
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 WhyDonate – FREE Donate button – Crowdfunding – Fundraising plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the remove_row function in all versions up to, and including, 4.0.15. This makes it possible for unauthenticated attackers to delete rows from the wp_wdplugin_style table.
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 WhyDonate WordPress plugin has a broken access control vulnerability where the remove_row function lacks a capability check, allowing unauthenticated attackers to delete arbitrary rows from the wp_wdplugin_style database table.
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.
-
Locate the WhyDonate plugin installationCheck the WordPress plugins directory at wp-content/plugins/ for a folder named whydonate, whydonate-fundraising, or similar WhyDonate-related folder. Also check wp-content/plugins/whydonate/ for the main plugin files.Affected if The plugin folder exists in wp-content/plugins/
-
Determine the installed versionOpen the main plugin file (usually plugin.php or whydonate.php) and locate the Version header in the plugin comment block, or check the version defined in any version constant/file within the plugin directory.Affected if The installed version is lower than 4.0.16 (for example 4.0.15, 4.0.14, etc.)
-
Verify the plugin is activeIn the WordPress admin, go to Plugins > Installed Plugins and check if WhyDonate is activated, or query the wp_options table for option_name = 'active_plugins' and check if whydonate is listed.Affected if The plugin shows as Active in WordPress or is present in the active_plugins option
-
Check for the vulnerable remove_row functionSearch the plugin files for the remove_row function definition. In the plugin directory, use grep or manually inspect the source files to locate function remove_row or similar.Affected if The remove_row function exists in the plugin code without a current_user_can or capability check before the row deletion logic
-
Confirm the wp_wdplugin_style table existsAccess the WordPress database (via phpMyAdmin or mysql CLI) and run SHOW TABLES LIKE 'wp_wdplugin_style' (replace wp_ with the actual table prefix).Affected if The wp_wdplugin_style table exists in the database
If WhyDonate is installed, active, and the version is below 4.0.16, the site is vulnerable to unauthenticated row deletion in the wp_wdplugin_style table.
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 dataUpdate the plugin to version 4.0.16 or later which adds proper authorization checks to the remove_row function, preventing unauthenticated access.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10186 — 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-10186 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